Siebel Partner Relationship Management Administration Guide > Setting Up Siebel PRM > Configuring Visibility for Siebel PRM >

Configuring Visibility

If your business model requires other visibility enhancements beyond these, you can configure visibility using the methods in the following topics:

• Configuring Visibility of Pop-Up or Pick Applets in Siebel PRM
• Configuring Visibility of Child Objects in Views
• Allowing Users to Change the Primary on a Visibility Team

Configuring Visibility of Pop-Up or Pick Applets in Siebel PRM

Pop-up visibility determines what data is shown when a pop-up pick applet is displayed. For example, when a user associates a contact with an account, or adds a sales representative to the sales team. For more information about configuring visibility of pop-up or pick applets, see Siebel Security Guide.

Configuring Visibility of Child Objects in Views

Siebel Business Applications use a number of visibility types to determine what data is shown on each view.

For example, the My Opportunities view uses Sales Rep visibility; it shows the opportunities for users on the Sales Team. If you have access to that Opportunity, you can also see its child objects. For example, you can see Activities, Contacts, and Quotes that are associated with that Opportunity.

Sometimes it is important to limit the visibility to the child objects. For example, if you are sharing Opportunities with your partners, you might want to show them any Activities, Contacts, and Quotes that they have added for that Opportunity, but not ones that you have added.

To meet this business requirement, Siebel Business Applications have added two capabilities.

You can apply a visibility type to an applet as a property of the View Web Template Item, which is where applets are associated with views. However, you cannot apply the Auto All property to the Web template item. For parent-child views such as Opportunity, Contacts, placing visibility on the Contacts applet on the View Web Template Item object changes the visibility on the Contacts applet when it is used in this view. Using this method, you can apply visibility to the applet in the context of a specific view, but reuse the applet with no visibility or other visibility applied in another view.

Alternatively, you can set visibility on the link object, and it is applied in addition to the visibility set at the view level. For parent-child views (such as Opportunity/Contacts) you can set a visibility type as a property on the Link object that links the Opportunity and Contact business components for this view. In addition, you can set the Auto All property on the Link object to override the visibility type set on the Link object. For example, if the visibility on the link is Sales Rep, but Auto All is true, administrative users still see all records in the Siebel database. Note that once visibility is applied to the link, it is applied wherever the link is used throughout the Siebel Business Application.

Allowing Users to Change the Primary on a Visibility Team

Siebel Business Applications use visibility teams to determine what data is displayed in different views. There are both position- and organization-based visibility teams.

For example, the My Opportunity view is position-based; it shows opportunities where the user is on the Sales Team. The All Opportunities view is organization-based; it shows opportunities where the user's organization is on the organization team.

Both position- and organization-based visibility teams have primary members.

On position-based teams, the primary member is the only user who can delete the data. The primary member is also used occasionally in Forecasting and Analytics to determine which organization is credited for certain metrics. On organization-based teams, the primary on the organization team is also important in measuring results on certain metrics.

The developer can either restrict the ability to change the primary team member to the manager of the primary on the position team, or give this ability to all users. By default, for position-based teams, only the primary's manager can change the primary. By default, for organization-based teams, any user can change the primary organization.

To change the default behavior, the developer must add a user property to the business component called MVG Set Primary Restricted, with the following syntax:

• Name: MVG Set Primary Restricted: [visibility mvlink name]
• Value: TRUE or FALSE

NOTE:  Users cannot directly delete the primary record from a position team. To delete the primary from the position team, you must go through a two-step process: first, designate a new member of the position team as primary, and then delete the original primary from the position team.