Deploying a Predefined Routing Model

You must determine if it is feasible to deploy the predefined routing models that are described in Predefined Routing Models.

To deploy a predefined routing model

1. Analyze the usage patterns for the user.

   Identify the data that the user requires and does not require when using Siebel Remote locally.

2. Compare the usage pattern with the definition of each routing model.

   Each routing model meets the requirements for a usage pattern.

3. Examine your Siebel installation and consider the following:

   1. Did you modify any of the views that are assigned to the Siebel Responsibilities?

      For more information, see Example of How Modifying a View Might Compromise Data Integrity.

   2. Did you modify any of the Siebel Responsibilities by adding new views that are accessible in local mode?

      For more information, see What Happens If a View Does Not Reference a Routing Rule.

   3. Has a custom foreign key been exposed in a Siebel view and business component?

      Siebel Remote might not support a custom foreign key. As a result, it does not route data to support the foreign key. If the user modifies or even views any base record that contains this foreign key in the local database, then Siebel Remote might inadvertently reset the reference to null, and then synchronize this modification to the Siebel Server.

4. If the answer to any question in Step 3 is yes, then you do not use the predefined routing models.

5. If the answer to the questions in Step 3 is no, then you can conduct a field test with a small group of representative users:

   1. Use predefined routing models.

      For more information, see Predefined Routing Models

   2. Assess how the predefined routing models affect the Transaction Router server component.

      For more information, see Expected Results from the Field Test of a Predefined Routing Model.

6. If the results from the field test are acceptable, then you can deploy the routing models to users.