|Bookshelf Home | Contents | Index | PDF|
If data in Siebel Business Applications and Microsoft Exchange Server has been modified in such a way that SSSE cannot synchronize the differences, SSSE resolves the conflict by using the Siebel data.
An example of a synchronization conflict is where the status of a Microsoft Exchange task is set to a value that differs from the value of the corresponding Siebel task item. If the status is updated at approximately the same time, thereby falling within the same synchronization cycle, SSSE has no way to determine which update has to be applied, and automatically preserves the Siebel data which is synchronized to Microsoft Exchange.
You can change the default behavior of SSSE so that when synchronization conflicts occur, SSSE resolves the conflicts by preserving the Microsoft Exchange data instead of the Siebel data, and synchronizes this data to Siebel CRM. To configure SSSE to use Microsoft Exchange data by default when synchronization conflicts occur, perform the steps in the following procedure.
|Siebel Server Sync Guide||Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.|