Expected Results from the Field Test of a Predefined Routing Model

The following table describes the results that you can expect from a successful field test.

Expected Result	Description
The size of the local database and the amount of data that Siebel Remote synchronizes decreases.	These metrics must be smaller if you use a predefined routing model when compared to your previous routing model.
The user can still do business tasks.	Data must not be missing that prevents the user from completing a critical business process.
Synchronization times decrease.	The predefined routing model must result in a shorter synchronization time than the synchronization time that Siebel Remote experiences if you use the previous routing model.
Siebel Remote routes every server transaction to the remote client except for those transactions that the routing models explicitly exclude.	If Siebel Remote does not route every transaction, then the user responsibility might not match the routing model.
Every view that accesses data on the Siebel Server displays the same data on the remote client.	If every view that accesses data on the Siebel Server does not display the same data on the remote client, then there is a strong possibility that you included incorrect views in the user responsibility.