Keeping Organization Information Current on the Remote Client

Modifications that you make to your organization, such modifying a position, division, or territory, can cause routers to reevaluate visibility for objects that are related to these modified objects. These modifications can affect Transaction Router performance and can result in a large backlog of transactions.

The remote client environment requires a value of Active. Siebel Remote creates progressively more transactions the higher in the hierarchy where you modify, add, or delete a position. The Transaction Processor and the Transaction Router might require a significant amount of time to work through the backlog and route these modifications to users. You can do the following to improve throughput:

• Keep organization information current on the remote client

• Use multiple routers

To keep organization information current on the remote client

• Reextract users after you modify your organization.

  Caution: For important caution information about modifying a position for a user or modifying a routing model, see Requirements for Extracting the Server Database.

For more information, see About the Standard Routing Model.