Exceptions to PolicyCenter synchronization updates

There are some cases in which PolicyCenter cannot perform a contact change or update:

• ContactManager notifies PolicyCenter that a contact has been deleted, but the contact is being used on at least one account in PolicyCenter.

  This case is not likely to happen, because ContactManager checks to see if a contact can be deleted before it sends the request to delete the contact to PolicyCenter. However, if this case does happen, PolicyCenter unlinks the contact, does not delete the local instance, and creates an activity warning that an external system tried to delete the contact.

• ContactManager notifies PolicyCenter that an address has been deleted, but the address is being used as a policy address in PolicyCenter.

  In this case, PolicyCenter unlinks the local instance of the address and does not delete it.

• PolicyCenter sends changes to a contact’s data to ContactManager, but the contact’s data was changed previously by another application or directly in ContactManager. The original data for the contact in PolicyCenter, prior to the change, must match the data currently in ContactManager for the change to be accepted. Since the original data that PolicyCenter sent does not match, ContactManager sends an exception to PolicyCenter and does not update the contact’s data.

  In this case, PolicyCenter creates an activity for a user to reapply the updates to the contact's data. The activity contains information about the contact and the data that could not be applied in ContactManager.