Bookshelf Home | Contents | Index | Search | PDF |
Configuration Guidelines > Visibility > Docking Visibility and Dock Objects >
Dock Object Visibility Rules
Dock Object Visibility rules are used only for limited visibility objects. They determine which records are routed to the mobile user. As an example, consider the Opportunity dock object. Rules exist to route records for which the user is on the sales team for the opportunity, or for which you are the manager of an employee on the sales team, or for opportunities that are available through drilldown. However, there are many more records available. To determine the sequence in which rules are evaluated, sort the list on descending Visibility Strength and then on ascending Sequence. Once a rule evaluates to true, no further rules are evaluated.
There are seven types of Dock Object visibility rules:
- E-type rule, Employee. An Employee is associated to the logical record. For example, the user is an owner of a service request record.
- F-type rule, Manager Of Employee. The subordinate of the user (a manager) is associated to the logical record. For example, the user is the manager of another user who owns a service request record.
- P-type rule, Position. A position is associated to the logical record. For example, if you are on the sales team for an account, you will receive the account record.
- Q-type rule, Manager Of Position. The subordinate of the user (a manager) is associated to the logical record. For example, the user is the manager of another user who is the primary on an account team.
- N-type rule, Node (Selective Account Retrieval). Used for selective account retrieval. This visibility rule is used to restrict the list of accounts routed to individual users by transferring only the accounts each salesperson needs, instead of all accounts to which the salesperson has visibility when connected to the server database. Selective retrieval is implemented through a combination of disabling a dock object visibility rule and adding account names to mobile clients in an administrative view. Disabling a visibility rule affects all mobile users accessing the server, so when considering this type of change, consult with Siebel Expert Services first.
- S-type rule, SQL Statement. Routes data based on a specific SQL select statement that is defined as part of the rule. For example, the rule to route an account that has been deemed as enterprise-visible uses a SQL statement to route based on the value of the ENTERPRISE_FLG column.
- C-type, Check Dock Object. Evaluates a secondary object. If the object being checked is retrieved with a Visibility Strength that is greater than or equal to the Check Dock Object Strength of the rule, then the rule evaluates to true. For example, for the Organization (Account) Dock Object, the Contact object is checked to be sure that if you have visibility to a contact, you also receive the records containing the contact's account.
Bookshelf Home | Contents | Index | Search | PDF |
Configuration Guidelines Published: 18 April 2003 |