Predefined Routing Models for Siebel Remote
The following table describes the routing models that come predefined with Siebel Remote. If your implementation uses a routing model, then Siebel Remote does a database extract and routes subsequent transactions to the user that are relevant to the job role that the name of the routing model describes, such as salesperson. To examine the views that some routing models reference, see Using Responsibilities to Route Data.
Routing Model | Description |
---|---|
Analyst |
The Analyst routing model routes the following data:
The analyst also receives activities but only those activities that are related to quotes, opportunities, or service requests. Siebel Remote also routes Project Items, such as the following:
|
Consultant |
The Consultant routing model allows a limited use license for the professional services functionality. It routes data only for the following items:
|
Executive Management |
The Executive Management routing model is an extract-only routing model for an executive manager. It allows this manager to use the remote client to do everyday tasks. It excludes all manager rules so that Siebel Remote routes to remote clients only that data that is visible. |
Field Engineer |
The Field Engineer routing model routes data that the user requires to do and debrief a complex job that requires an acceptable level of historical data regarding customer and asset history. The Field Engineer can use this data to do the following work:
Debriefing is the reporting of material usage, time, and expenses to service managers after the user completes an activity. |
Field Sales Manager |
The Field Sales Manager routing model routes data that is typical for the Sales Representative Standard, but it also includes team data for accounts, contacts, and opportunities. |
Field Sales Representative |
The Field Sales Representative routing model routes data that is relevant to a salesperson. |
Field Technician |
The Field Technician routing model routes data that is relevant to a field technician. |
Life Science User |
The Life Science User routing model is similar to the Mobile Client - Standard routing model except that it routes more data to remote clients and contains some extra rules that the Siebel Life Sciences applications require. These extra rules are for the following dock objects:
|
Minimal Data |
The Minimal Data routing model routes data only for the following items:
|
Mobile Client - Extract Only |
The difference between the Mobile Client - Extract Only routing model and the Mobile Client - Standard routing model is that the Mobile Client - Extract Only routing model does not enable synchronization. A local database that uses the Mobile Client - Extract Only routing model reflects a snapshot of application data with respect to the user. |
Mobile Client - Standard |
Unlike other routing models, the Mobile Client - Standard routing model routes the full set of data that is related to the user, according to the configuration of the visibility rules in the Siebel runtime repository. There are some exceptions. For more information, see About the Standard Routing Model. |
Mobile Partner User |
The Mobile Partner User routing model routes data that is relevant to the Partner Sales position and the Service Representative position who use a mobile version of the Siebel PRM Partner Portal application. This model includes the following items:
|
Selective Retrieval |
The Selective Retrieval routing model routes data that allows the user to use individual records that Siebel Remote synchronizes to the remote client. Siebel CRM releases support the selective retrieval functionality for the following objects:
For more information, see Selective Retrieval Routing Model. |
Senior Field Engineer |
The Senior Field Engineer routing model routes data that supports the following:
|