What Happens If a View Does Not Reference a Routing Rule

A view typically references a routing rule that supports an object that possesses limited visibility. If you add a view that does not reference a corresponding routing rule, then Siebel Remote does not synchronize any data for that view. If you add this view to a responsibility, and if your implementation uses Client Wins to resolve an update conflict, then the following undesirable situation might occur:

1. A user uses the new view on the remote client to create a new record.

2. The user synchronizes with the Siebel Server.

3. The user of a Web client modifies the same record on the Siebel Server.

4. The user synchronizes but does not see the updates that the user of the Web client made to the record.

5. The user modifies the record in the remote client.

6. The user synchronizes and overwrites the content of the record that resides on the Siebel Server.

   In this situation, the user unintentionally overwrites the updates that another user makes to a same record.