User Guide

The functionality for Visibility Levels feature is primarily restricted to System Administrators in order to setup and configure models to limit access to certain packages in a model. For the most part general users will not be aware of Visibility Levels, they simply just won't see certain packages in the model.

Defining Visibility Level aware Database Managers

For the most part defining Database Managers in the Professional version of Sparx Systems Cloud Service Configuration Client is the same as the regular version, with the following exceptions:

Oracle

All Oracle connections will need a 'DefaultSchema={schema_name};' option manually added to the connection string. Where {schema_name} is the physical name of the schema that owns the Enterprise Architect tables. For example:

Provider=OraOLEDB.Oracle.1;Password=pass;Persist Security Info=True;User ID=user1;Data Source=ORA_SN;DefaultSchema=owner_user;

In a typical Oracle connection to a Enterprise Architect model the 'User ID' option is both the owner of the tables and user credentials that are being used to access the data. However a model with Visibility Levels these option need to be different accounts/users, so the DefaultSchema option has been added.

Microsoft SQL Server

All SQL Server connections will need an Alias value defined that uniquely identifies the database manager on the current server. The Alias value is the name that Enterprise Architect users knows the model by.

In previous versions of Cloud Service the database manager alias for SQL Server based connections was automatically determined by the database name, which meant that each SQL Server database could only ever have one database manager defined in the Cloud Service, now with the use of the Alias field a single database can have an unlimited number of database managers defined.

Enabling Pro Features on a Database Manager

In order for the Pro Cloud Server to allow the use of Visibility Levels in a model the 'Pro Features' option must be checked. This is achieved by opening the Sparx Systems Cloud Services Configuration Client application (SSProCloudClient.exe) connecting to the appropriate server. Then selecting the database manager in the list and clicking Configure. On the 'Configure Database Manager' screen check the 'Pro Features' option.

Set a Package's Visibility Level

From within Enterprise Architect, a Package's Visibility Level can be set using the Project Browser context menu item Package Control | Set Visibility Level...

This menu item will only be available in models that have been setup for Visibility Levels and when they are being accessed via a Pro Cloud server connection.

Once a visibility level has been set on a Package, that Package and all of it children will only be able to be viewed, accessed and updated by users with the appropriate visibility level.

To remove a visibility level from a Package (and all its children), simply set the Visibility Level back to zero.

Visibility Levels users can apply

Users can only set the Visibility Levels on packages to levels up-to (and including) the highest level they have been assigned. For example a user that has been assigned level 3 can update the Visibility Level of a any package from anything between 0 and 3.