14How Siebel CRM Desktop Maps Fields Between Siebel CRM Data and IBM Notes Data

How Siebel CRM Desktop Maps Fields Between Siebel CRM Data and IBM Notes Data

This chapter describes how Siebel CRM Desktop maps fields between Siebel CRM data and IBM Notes data. It includes the following topics:

• How Siebel CRM Desktop Maps Fields Between Siebel Activities and IBM Notes Calendar

• How Siebel CRM Desktop Maps Fields Between Siebel Activities and IBM Notes To Do Items

• How Siebel CRM Desktop Maps Fields Between Siebel CRM Activities and IBM Notes Emails

• How Siebel CRM Desktop Transforms Objects Between Siebel CRM Data and IBM Notes Data

How Siebel CRM Desktop Maps Fields Between Siebel Activities and IBM Notes Calendar

The following table describes how Siebel CRM Desktop maps objects between a Siebel CRM activity and IBM Notes Calendar.

Siebel Field	IBM Notes Field	Required	Description
Account	Account association that the user specifies when the user links a CRM record.	No	Not applicable.
Comments	Description A private calendar entry does not include a description.	No	Not applicable.
Contacts	List of contacts that is received from the list of participants that remain after employees are removed from this list when Siebel CRM Desktop resolves the primary email of the contacts.	No	The logic that applies for the Employees field also applies for the Contacts field.
Created by	User ID of the employee who creates the activity.	Yes	Not applicable.
Created Date	Timestamp of when the activity is created.	Yes	Not applicable.
Description	For more information, see How Siebel CRM Desktop Handles Private Activities.	No	The value that is set for a private To Do item is defined in the customization package and is included in the localization resources.
Duration	Duration	Yes	Not applicable.
Employees	List of employees that is received from the list of participants when Siebel CRM Desktop resolves the primary email of the employees.	No	Siebel CRM Desktop does the preliminary resolution when the user saves a calendar entry. To improve the quality of this list, the Siebel Server analyzes the processing that occurs on the server. It does this work after the next synchronization.
ExceptionsList	No direct mapping to the IBM Notes field exists.	Yes	For more information, see How Siebel CRM Desktop Handles a Repeating Calendar Entry.
Meeting Location	Location	No	Not applicable.
Opportunity	Opportunity association that the user specifies when the user links a CRM record.	No	Not applicable.
Owner	For more information, see How Siebel CRM Assigns Meeting Organizers.	Yes	Not applicable.
PIM Meeting Participants	List of participants for the calendar entry, delimited by a semicolon (;).	No	Not applicable.
Planned	Start Date/Time	Yes	Not applicable.
Planned Completion/End time	End Date/Time	Yes	Not applicable.
Priority Values are: 1-ASAP 2-High 3-Medium 4-Low	IBM Notes priority Values are: 1-High 2-High 3-Medium 4-Low	No	For more information, see How Siebel CRM Desktop Maps the Priority Field.
Private	Private	No	Not applicable.
Repeat	Recurring flag	No	Not applicable.
Repeat Frequency	Siebel CRM Desktop uses a binary field that combines the data from a number of IBM Notes fields. The frequency is daily, weekly, monthly, or yearly.	No	Not applicable.
Repeat Until	Recurrence Range End	No	Not applicable.
Type	Type that the user specifies when linking the CRM record. The default value is Calendar Entry.	Yes	The user can choose the activity type in the form of the IBM Notes calendar entry only for an activity that contains the following Display in value: Calendar and Activities The customization package defines the default value. You can change this value.

How Siebel CRM Desktop Handles Private Activities

Siebel CRM Desktop handles a private activity in the following ways:

• If an activity in Siebel CRM is marked private, then it does not synchronize this activity from the Siebel Server to IBM Notes. The master filters in the customization package restrict it from synchronizing a private activity.

• If the user creates a private activity in IBM Notes and then attempts to share it with Siebel CRM, then validation disallows this attempt. For example, assume a user creates a shared activity in a Siebel CRM calendar entry. If the user attempts to mark this calendar entry as private, then Siebel CRM Desktop displays a warning message that it cannot share a private IBM Notes item with Siebel CRM.

How Siebel CRM Desktop Maps the Priority Field

Siebel CRM data includes an ASAP priority value but IBM Notes data does not. It is not possible to save the ASAP value during synchronization, so Siebel CRM Desktop does not include it in the mapping. If a Siebel task is marked 1-ASAP, then Siebel CRM Desktop creates a mapping error.

The IBM Notes activity includes another field to store the Priority value that Siebel CRM Desktop derives from the Siebel CRM data. Note the following behavior:

• If the IBM Notes item is updated, and if the Priority of the IBM Notes item is High, then Siebel CRM Desktop validates the stored value.

• If the value that is stored for the activity is ASAP, then Siebel CRM Desktop uses the ASAP value from the activity.

• If the value that is stored for the activity is not ASAP, then Siebel CRM Desktop uses the value from the IBM Notes record.

How Siebel CRM Desktop Maps Fields Between Siebel Activities and IBM Notes To Do Items

The following table describes how Siebel CRM Desktop maps fields between a Siebel CRM activity and the IBM Notes To Do item.

Siebel Field	IBM Notes Field	Required	Description
Owner	Owner	Yes	For more information, see How Siebel CRM Desktop Maps the Owner Field Between Siebel CRM Activities and IBM Notes To Do Items.
Type	The type that the user specifies when the user links a CRM record. The default value is To Do.	Yes	If a user shares a To Do item, then Siebel CRM Desktop creates an activity in IBM Notes with a Display in value that includes the following: To Do and Activities The customization package defines the default value. You can change this value.
Description	For more information, see How Siebel CRM Desktop Handles Private Activities.	No	The customization package defines the value that is set for a private To Do item. Localization resources include this value.
Priority Values are: 1-ASAP 2-High 3-Medium 4-Low	IBM Notes priority Values are: 1-High 2-High 3-Medium 4-Low	No	For more information, see How Siebel CRM Desktop Maps the Priority Field.
Comments	Description A private To Do item does not include a description.	No	If the Private check box is set to allow a shared To Do item, then Siebel CRM Desktop sets the Comments field to a value that the customization package defines, such as Unavailable.
Start Date	Start Date	No	The Start Date for an activity is the start date that the user sets for a To Do item. If the user does not enter the start date, then the start date for the activity is also empty.
Done	Completed Date	No	The Done date is the date that Siebel CRM displays as the Actual End date in the Siebel Web Client.
Completed flag	Completed flag	No	Not applicable.
Due	Due Date	No	Not applicable.
Percent complete	Percent complete	No	The value of the Percent complete field is related to the status. For more information, see How Siebel CRM Desktop Maps the Status Field of an Activity.
Status	Status	No	For more information, see How Siebel CRM Desktop Maps the Status Field of an Activity.
Account	Account association that the user specifies when the user links a CRM record.	No	Not applicable.
Opportunity	Opportunity association that the user specifies when the user links a CRM record.	No	Not applicable.
Contacts	Contact association that the user specifies when the user links a CRM record.	No	Not applicable.
Created by	User ID of the employee who creates the activity.	Yes	Not applicable.
Created Date	Timestamp of when the activity is created.	Yes	Not applicable.

How Siebel CRM Desktop Maps the Owner Field Between Siebel CRM Activities and IBM Notes To Do Items

This topic describes how Siebel CRM Desktop maps the owner field between a Siebel CRM activity and the IBM Notes To Do item. Siebel CRM Desktop sets the owner differently for each of the following situations:

• A shared To Do item is assigned to another employee. It sets the assignee as the owner of the activity.

• A shared To Do item is assigned to a number of employees. It sets each assignee as the owner of their own activity.

• A shared To Do item is assigned to a shared contact or to an external person. It sets the employee who created the To Do item as the owner of the activity.

• A To Do item is created by an external person and assigned to an employee and this employee shares the To Do item. It sets the employee as the owner of the activity.

• An external person who is not a Siebel employee sends a To Do item to a number of employees who are Siebel CRM Desktop users. It sets each employee as the owner of the activity and adds the remaining employees to the employee team. It does this work after each employee accepts and shares the To Do item.

How Siebel CRM Desktop Maps the Status Field of an Activity

The following table describes how Siebel CRM Desktop maps the status of a Siebel CRM activity to the status of the IBM Notes To Do item when the user shares a To Do item.

Siebel Status	IBM Notes Status
Not Started	Not Started
In Progress	In Progress
Done	Completed
On Hold	Waiting on someone else
Canceled	Deferred

The following table describes how Siebel CRM Desktop maps the Status field of a Siebel CRM activity when the value of the Display In field of a To Do activity contains the following value:

To Do and Activities

Siebel CRM Desktop does this work during synchronization.

Siebel Status	IBM Notes Status
Not Started/Acknowledged	Not Started
In Progress	In Progress
Done	Completed
On Hold	Waiting on someone else
Canceled/Declined	Deferred
Any other value	The logic described in the following table determines the value for the status.

The following table describes how Siebel CRM Desktop uses the Percent Complete value in the IBM Notes To Do item to determine the value of the Status field.

Siebel Status	Value of Percent Complete for the IBM Notes To Do Item
Not Started	0
In Progress	Greater than zero and less than one hundred
Completed	100

Scenario for Mapping the Status Field of an Activity

This topic gives one example of how Siebel CRM Desktop maps the status field of an activity. The following sequence occurs:

1. A user creates a shared To Do item in IBM Notes that includes a status that is In Progress and a Percent Complete that is 0.

2. Siebel CRM Desktop creates an activity on the Siebel Server that includes a status of In Progress.

3. The user synchronizes with the Siebel Server.

4. On the Siebel Server, Siebel CRM Desktop changes the status to Requested.

5. The user synchronizes with the Siebel Server again.

6. In IBM Notes, Siebel CRM Desktop updates the activity status to Requested.

7. At this point, the Percent Complete field of the To Do item is 0. Siebel CRM Desktop updates the To Do item status to Not Started.

How Siebel CRM Desktop Maps Fields Between Siebel CRM Activities and IBM Notes Emails

The following table describes how Siebel CRM Desktop maps fields between a Siebel CRM activity and the IBM Notes email.

Siebel CRM Field	Required	IBM Notes Field
Type	Yes	One of the following: If the user is the receiver, then Email - Inbound If the user is the sender, then Email - Outbound
Description	No	Email Subject
Display	Yes	Changes to Communication and Activities. This value is the default value.
Email Attachment Flag	No	Changes to Y. This value is the default value.
Email BCC Line	No	Email BCC Line
Email Body	No	Email Body
Email CC Line	No	Email CC Line
Email Sender Address	No	Siebel CRM Desktop maps part of the value in the From Line to the Email Address. For example, assume the From Address includes the following address: Jane Smith, or Jane Smith <[e-mail]> In this example, Siebel CRM Desktop resolves the Email Sender Address to the following address: [e-mail]
Email Sender Name	No	Siebel CRM Desktop maps part of the From Line to the Display Name. For example, using the example from the Email Sender Address, the Email Sender Name resolves to Jane Smith.
Email To Line	No	Email To Line.
Priority	No	Importance. Siebel CRM Desktop applies the following mapping: 1-ASAP in Siebel CRM data is ASAP in IBM Notes 2-High in Siebel CRM data is High in IBM Notes 3-Medium in Siebel CRM data is Normal in IBM Notes 4-Low in Siebel CRM data is Low in IBM Notes For more information, see How Siebel CRM Desktop Maps the Priority Field.
Account Id	No	The Primary account association that the user specifies when the user creates the activity.
Opportunity Id	No	The opportunity association that the user specifies when the user creates the activity.
Attachment	No	The original email that Siebel CRM Desktop saves as an attachment to the activity.

How Siebel CRM Desktop Transforms Objects Between Siebel CRM Data and IBM Notes Data

This topic describes how Siebel CRM Desktop transforms objects between Siebel CRM Data and IBM Notes data. It includes the following topics:

• How Siebel CRM Desktop Transforms a Calendar Entry That Does Not Repeat

• How Siebel CRM Desktop Transforms a Repeating Calendar Entry That Matches a Siebel Repeating Pattern

• How Siebel CRM Desktop Transforms a Repeating Calendar Entry That Does Not Match Siebel Repeating Patterns

• How Siebel CRM Desktop Transforms Siebel CRM Activities That Do Not Repeat

• How Siebel CRM Desktop Transforms Siebel CRM Activities That Repeat

• How Siebel CRM Desktop Maps Fields Between a Siebel Calendar Entry and a IBM Notes Calendar Entry

If the user synchronizes a repeating activity between the Siebel Server and IBM Notes, then Siebel CRM Desktop uses the following logic:

1. Maps changes between Siebel activities in IBM Notes and native IBM Notes items.

   Siebel CRM Desktop updates changes in the IBM Notes Calendar entry in the activity that is linked to the Calendar entry.

2. Synchronizes changes between Siebel activities in IBM Notes and Siebel CRM activities.

   Siebel CRM Desktop updates this change in Siebel CRM data after the synchronization finishes.

How Siebel CRM Desktop Transforms a Calendar Entry That Does Not Repeat

The following table describes how Siebel CRM Desktop transforms a Calendar entry in IBM Notes that does not repeating.

Action in IBM Notes	Work That Siebel CRM Desktop Performs
The user creates an activity that does not repeat in IBM Notes.	Creates a corresponding Siebel CRM activity.
The user changes an activity that does not repeat in IBM Notes.	Changes the corresponding Siebel CRM activity.
The user deletes an activity that does not repeat in IBM Notes.	Deletes the corresponding Siebel CRM activity.
The user changes an activity that does not repeat in IBM Notes to a repeating Calendar entry that matches the Siebel repeating pattern.	Changes the corresponding Siebel CRM activity.
The user changes an activity that does not repeat in IBM Notes to a repeating Calendar entry that does not match the Siebel repeating pattern.	Siebel CRM Desktop does the following work: Changes the corresponding activity. It uses the Siebel repeating pattern that contains the longest interval between occurrences and that can incorporate all occurrences of the chosen IBM Notes pattern. To match the calendars in Siebel CRM and in IBM Notes, it identifies the list of exceptions for the activity.

How Siebel CRM Desktop Transforms a Repeating Calendar Entry That Matches a Siebel Repeating Pattern

The following table describes how Siebel CRM Desktop transforms a repeating Calendar entry that matches a Siebel CRM repeating pattern.

Action in IBM Notes	Work That Siebel CRM Desktop Performs
The user creates a repeating Calendar entry that matches a Siebel repeating pattern.	Creates a corresponding Siebel CRM repeating activity.
The user changes a single occurrence for a repeating Calendar entry that matches a Siebel repeating pattern.	Siebel CRM Desktop does the following work in IBM Notes: Adds the date of the exception that changed to the exceptions list for the target activity. Adds the new, nonrepeating activity to the newly created calendar entry in IBM Notes.
The user changes a repeating Calendar entry that matches a Siebel repeating pattern.	Changes the corresponding Siebel CRM repeating activity.
The user deletes a single occurrence for a repeating Calendar entry that matches a Siebel repeating pattern.	Siebel CRM Desktop does the following work in IBM Notes: Adds the date of the exception to the exceptions list for the target activity. Deletes this single occurrence of the activity.
The user changes a repeating Calendar entry that matches a Siebel repeating pattern into the Calendar entry that does not repeat.	Changes the corresponding Siebel CRM activity to an activity that does not repeat.
The user changes a repeating Calendar entry that matches a Siebel repeating pattern into a repeating Calendar entry that does not match any Siebel repeating patterns.	Siebel CRM Desktop does the following work in IBM Notes: Changes the corresponding Siebel CRM activity. It uses the Siebel repeating pattern that contains the longest interval between occurrences and that can incorporate all occurrences of the chosen IBM Notes pattern. To match IBM Notes and Siebel calendars, it identifies the list of exceptions for this activity.

How Siebel CRM Desktop Transforms a Repeating Calendar Entry That Does Not Match Siebel Repeating Patterns

The following table describes how Siebel CRM Desktop transforms a repeating Calendar entry that does not match a Siebel repeating pattern.

Action in IBM Notes	Work That Siebel CRM Desktop Performs
The user creates a repeating Calendar entry that does not match a Siebel repeating pattern.	Siebel CRM Desktop does the following work in IBM Notes: Creates the corresponding activity. To identify this activity, it uses the Siebel repeating pattern that contains the longest interval between occurrences and that can incorporate all occurrences of the chosen IBM Notes pattern. To match the calendars in IBM Notes and Siebel CRM Desktop, it creates the list of exceptions for this activity.
The user changes a single occurrence for a repeating Calendar entry that does not match any Siebel repeating pattern.	Siebel CRM Desktop does the following work in the IBM Notes Calendar: Creates a new calendar entry that is nonrepeating. Deletes the occurrence that changed for the IBM Notes calendar entry. Creates an exception in IBM Notes for the occurrence date that changed. Siebel CRM Desktop does the following work in IBM Notes: Adds an exception to the exceptions dates list of the activity. Adds a new activity that does not repeat.
The user deletes a single occurrence for a repeating Calendar entry that does not match a Siebel repeating pattern.	Siebel CRM Desktop does the following work in IBM Notes: Adds an exception to the exceptions dates list of the activity. Deletes this single occurrence of the activity.
The user deletes a repeating Calendar entry that does not match a Siebel repeating pattern.	Deletes the corresponding repeating activity.

How Siebel CRM Desktop Transforms Siebel CRM Activities That Do Not Repeat

The following table describes how Siebel CRM Desktop transforms a Siebel CRM activity that is not repeated.

Work That Occurs in Siebel CRM	Work That Siebel CRM Desktop Performs
The user creates a Siebel CRM activity that is not repeated.	Creates the corresponding IBM Notes activity that does not repeat.
The user changes a Siebel CRM activity that is not repeated.	Changes the corresponding IBM Notes activity that does not repeat.
The user changes a Siebel CRM activity that is not repeated to an activity that is repeated.
The user deletes a Siebel CRM activity that is not repeated.	Deletes the corresponding IBM Notes activity that does not repeat.

How Siebel CRM Desktop Transforms Siebel CRM Activities That Repeat

The following table describes how Siebel CRM Desktop transforms an activity in Siebel CRM that is repeated.

Work That Occurs in Siebel CRM	Work That Siebel CRM Desktop Performs
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 Siebel 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 Siebel 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 Siebel 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.	Siebel 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 Siebel CRM Desktop synchronizes from the Siebel Server

How Siebel CRM Desktop Maps Fields Between a Siebel Calendar Entry and a IBM Notes Calendar Entry

The following table describes how Siebel CRM Desktop maps some fields between a repeating Siebel calendar entry and a repeating IBM Notes calendar entry.

Siebel CRM		IBM Notes
Frequency	Start and End Date	Frequency	Occurrence	Start and End Date
Daily	Start Date Repeat Until	Daily	Every 1 day	Start is Start date End by is Repeat Until
Weekly	Start Date Repeat Until	Weekly	Every 1 week Weekday is the weekday of the Siebel Start Date	Start is Start date End by is Repeat Until
Monthly	Start Date Repeat Until	Monthly	Every 1 month Day is day of Siebel Start Date	End by is Repeat Until
Quarterly	Start Date Repeat Until	Monthly	Every 3 months Day is day of Siebel Start Date	End by is Repeat Until
Yearly	Start Date Repeat Until	Yearly	Date is date of the Siebel Start Date	End by is Repeat Until