Bookshelf v8.0: About Allowing or Preventing Record Deletions for a Domain

SSSE includes a setting called Allow Record Deletions for each Siebel domain and each PIM domain. The basic purpose of this setting is to let the administrator govern whether delete operations in one domain will affect the corresponding record in the domain to which it synchronizes. Specifically, the value of the Allow Record Deletions setting affects what happens in the following situations:

The following additional factors can also affect what happens in each of these situations:

The removal of a single occurrence of a recurring calendar item is not considered a delete operation and is not affected by the status of the Allow Record Deletions setting. That is, if you delete a single occurrence of a recurring Siebel appointment, the corresponding occurrence is deleted in Microsoft Exchange at the next synchronization. Similarly, if you delete a single occurrence of a recurring Microsoft Exchange appointment, the corresponding occurrence is deleted in the Siebel database at the next synchronization.

For information about how the Allow Record Deletions setting affects the Business Contacts, Personal Contacts, and Employee domains, see Table 27. (Synchronization of data from the Siebel Personal Contacts and Siebel Employee domains is not supported if you are using Microsoft Exchange 2010.) For information about how the Allow Record Deletions setting affects the Calendar and Tasks domains, see Table 28. For more information on how to specify the Allow Record Deletions setting, see Allowing or Preventing Record Deletions.

Table 27. Effect of Allow Record Deletion Setting on Contacts and Employees Records
Allow Record Deletion Selected?	Delete Operation Originated From	Destination System Behavior	Behavior After Future Record Modification
Yes	Siebel	PIM record is deleted.	Not applicable
Yes	PIM	Siebel personal contacts record is deleted. User is removed from Sync List for Siebel business contacts record. Siebel employees records are unchanged, because the Employees domain only allows one-way synchronization, from the Siebel record to the PIM record.	Not applicable
No	Siebel	The value in the Category field of the PIM record is deleted, but the rest of the record is not changed.	If the PIM record is modified but the Category field remains empty, then the changes are not synchronized. If the PIM record is modified and the Category field is set to a valid value (such as Siebel Contact), then the record is synchronized in such a way that a new record is created in the Siebel database.
No	PIM	For Business Contacts, Personal Contacts, and Employees domains, SSSE deletes its internal mapping between the PIM record and the Siebel record, but the Siebel record is not physically deleted. For domains where synchronization is configured to be bidirectional, the user is removed from the Siebel record's Sync List. For domains that only allow one-way synchronization (for example, the Employees domain), the user is not removed from the Siebel record's Sync List.	For domains where synchronization is configured to be bidirectional, future modifications to the Siebel record are not synchronized for the relevant user unless the user adds himself or herself to the record's Sync List again. This corresponds to the behavior of previous versions of SSSE. For domains that only allow one-way synchronization (for example, the Employees domain), future changes to the Siebel record are synchronized with PIM despite the earlier deletion of the PIM record, because that deletion originated on the PIM and was not allowed to affect the Sync List of the Siebel record.

Table 28 shows how the Allow Record Deletions setting affects the Calendar and Tasks domains.

Table 28. Effect of Allow Record Deletion Setting on Calendar and Tasks Records
Allow Record Deletion Selected?	Delete Operation Originated From	Inbound Activity Filtering Enabled?	PIM Domain Category Field Status	Destination System Behavior	Behavior After Future Record Modification
Yes	Siebel	Not applicable	Not applicable	Record is physically deleted from PIM.	No future modification is possible, since both PIM and Siebel records are deleted.
Yes	PIM	Not applicable	Not applicable	Record is physically deleted from the Siebel database.	No future modification is possible, since both PIM and Siebel records are deleted.
No	PIM	Not applicable	Not applicable	The Siebel record is not deleted. SSSE deletes its internal mapping between the PIM record and the Siebel record.	SSSE treats modification of the remaining Siebel record as if it were a new record. This causes the creation of a corresponding PIM record at the next synchronization.
No	Siebel	Yes	Field is specified (required when inbound activity filtering is enabled)	The PIM record is not deleted, but its Category field is cleared. SSSE deletes its internal mapping between the PIM record and the Siebel record.	SSSE treats modification of the remaining PIM record as if it were a new record. Whether or not the modified record synchronizes to Siebel depends on whether the Category field value is acceptable to Inbound Activity Filtering.
No	Siebel	Yes	Field is not specified (invalid when inbound activity filtering is enabled)	The PIM record is preserved unchanged. SSSE deletes its internal mapping between the PIM record and the Siebel record. An error message is logged.	SSSE treats modification of the remaining PIM record as if it were a new record. Whether or not the modified record synchronizes to Siebel depends on whether the Category field value is acceptable to Inbound Activity Filtering.
No	Siebel	No	Not applicable	The PIM record is preserved unchanged. SSSE deletes its internal mapping between the PIM record and the Siebel record.	SSSE treats modification of the remaining PIM record as if it were a new record. This causes the creation of a corresponding Siebel record at the next synchronization.

Siebel Server Sync Guide		Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.