Saving Transactions That Siebel Remote Does Not Include in an Extract

To prevent the loss of local transactions that a user might enter in the local database, you can use the Save Client Transactions parameter. This feature is valid for a typical reextract of the local database for the user. It does not work during a major upgrade or for records that Siebel Remote does not display for the user.

If Siebel Remote extracts a server database for a remote client, and if Save Client Transactions is TRUE, then Siebel Remote does the following:

1. Extracts transactions that it has not yet synchronized with the Siebel Server. It extracts these transactions from the current local database, and then stores them in the user inbox as DX files.

2. Replaces the current local database with the new extract.

3. Applies the DX files from the user inbox to the new local database. These files include the transactions that it has not yet synchronized with the Siebel Server.

4. Sends the transactions to the Siebel Server during the next synchronization.

To save client transactions that Siebel Remote does not include in an extract

• Make sure the Save Client Transactions parameter is set to TRUE.

  For more information, see Parameters of the Database Extract Server Component.

Strings That Siebel Remote Does Not Send to the Local Database

Siebel Remote does not send some strings to the local database. These strings reside in the S_MSG table. For example, some workflow processes include steps that use the Error Code property. When Siebel Remote extracts the server database for a local developer, it does not correctly route the records in the S_MSG table that the Error Code property uses.