The user creates a repeating activity in Siebel CRM.

Creates a corresponding repeating Calendar entry in IBM Notes.

The user changes a single occurrence of the repeating activity in Siebel CRM:

• Creates a delete activity.
• Creates a new activity that does not repeat.

Deletes the occurrence of the IBM Notes Calendar entry for the date of the occurrence that is deleted in Siebel CRM.

The user can modify a repeating activity in Siebel CRM. The activity was created in IBM Notes from a repeating Calendar entry, so the activity can originate in Siebel CRM or CRM Desktop can synchronize it to Siebel CRM from IBM Notes.

If the user changes all instances of the repeating activity in Siebel CRM, then CRM Desktop deletes every instance of the repeating activity from the current day forward. Any instances that exist before the current day remain on the calendar.

If the user deletes only one instance, then Siebel CRM still schedules every other instance.

If the user changes a repeating Siebel CRM activity, then CRM Desktop does the following work:

• Changes the following date of the initial activity to the date minus one occurrence:

  repeat until

• Creates a new repeated Calendar entry that the date of the change for the repeat determines. This situation is true until the date is the following date of the parent repeated Calendar entry:

  repeat until

• Relinks the delete records to the corresponding repeating activities, depending on the exception date.

CRM Desktop does the following work:

• Changes the end date of the initial repeating activity
• Creates a new repeating activity. The Siebel CRM activity determines this new repeating activity.
• Changes the links for the delete activities depending on the changes that CRM Desktop synchronizes from the Siebel Server