Bookshelf v7.5: Configuring Visibility Using Siebel Tools

Configuration Guidelines > Visibility > Record Access Visibility >

Configuring Visibility Using Siebel Tools

The following sections give more details on configuring team-based visibility settings.

This setting restricts access to members of a team for team-based business components. Examples of this setting include Opportunity, Contact and Account. You configure team-based visibility by setting the Owner Type, Visibility Field, Visibility Emp MVField, and the Visibility MVLink properties on the Business Component View Mode, which is a child object type of the business component. If you do not set the Owner Type, Visibility Emp MVField and the Visibility MVLink properties, these records will be visible to everyone.

The view visibility properties should be set to work with these Business Component View Mode properties as follows:

My View, which displays all records for which a user is on the team, should have the following properties:

Set the Visibility Applet property to identify the first applet defined in the Base definition of the View Web Template Item for the view.

Set the Visibility Applet Type property to Sales Rep (this is the default value if none is set).

My Teams View, which displays all records for which the manager or subordinates are the primary or owner, should have the following properties:

Set the Visibility Applet property to identify the primary applet in the view.

Set the Visibility Applet Type property to Manager.

All View, which displays all of the records within the organization (with a valid primary set), should have the following properties:

Set the Visibility Applet property to identify the Sector 0 applet in the view.

Set the Visibility Applet Type property to Organization.

All View Across Organizations, which displays all records across all organizations (with a valid primary set), should have the following properties:

Set the Visibility Applet property to identify the Sector 0 applet in the view.

Set the Visibility Applet Type property to All.

You must also consider the following:

If no visibility applet type is set, the application uses the most restrictive default type, which is team-based (for example, Sales Rep).

Do not make All, All...Across Organizations, and Admin Mode views available to mobile users. Using these views will confuse users and can lead to data integrity issues. Mobile users only have a small subset of records in their local database. A user with access to an All view could mistakenly assume that this is a complete list of all records, which it is not; it is limited to records that exist in the user's local extract. One of the potential consequences from this is data corruption. For example, a Primary Id can be reset from a valid value to No Row Match Id if a view exposes a record and its related records do not exist in the local extract.

In a production environment, use the Administration views to make sure the Local Access flag is set to False. When you are in a testing environment, you can set it to True.

An Administration view displays all the records in the database by disregarding any visibility properties. You configure this in Siebel Tools by setting the Admin Mode Flag to True and leaving the Visibility Applet and Visibility Applet Type properties blank.

Some data in your application will be visible with no constraints. This includes enterprise-visible data, such as tables that have a Docking Visibility Type of Enterprise.