How Siebel CRM Desktop Distinguishes Between Outlook Archive Items and Deleted Items
Siebel CRM Desktop does not distinguish between items in Outlook that Outlook archives and items that the user deletes. If Outlook archives an item, then Siebel CRM Desktop interprets this action as a deletion and it deletes the corresponding Siebel CRM record in the Siebel database. To modify this behavior, you can use the archive_activity_days variable in the business_logic.js file.
Siebel CRM Desktop does one of the following depending on the value of the end date that the deleted Outlook Calendar entry contains:
The end date occurs before the current system date minus the number of days that the archive_activity_days variable specifies. Siebel CRM Desktop does not delete the corresponding Siebel CRM record.
The end date occurs after the current system date minus the number of days that the archive_activity_days variable specifies. Siebel CRM Desktop deletes the corresponding Siebel CRM record.
Siebel CRM Desktop sets the archive_activity_days variable to 7, by default. For example, if you leave the archive_activity_days variable at the default value, then Siebel CRM Desktop does the following:
If a meeting occurred before the current system date minus 7 days, and if the meeting no longer exists in Outlook, then it treats the meeting as an archived item. It does not delete the corresponding Siebel CRM meeting from the Siebel database.
If the user schedules a meeting to occur less than 7 days before the current system date, then it assumes the user intentionally deleted the meeting and it deletes the corresponding Siebel CRM meeting from the Siebel database.
How Siebel CRM Desktop Handles Archived Items
If Outlook archives a To Do item, and if this To Do item no longer exists in Outlook, then Siebel CRM Desktop examines the Status field in the To Do activity. It then does one of the following depending on if the value in the Status field of the To Do activity is Done:
Done. It assumes the Siebel activity is an archived item and it does not delete the corresponding Siebel activity from the Siebel database.
Not Done. it assumes the user intentionally deleted the Siebel activity and it deletes the corresponding Siebel activity from the Siebel database.