Bookshelf Home | Contents | Index | PDF     

Siebel CRM Desktop for IBM Notes Administration Guide > How Siebel CRM Desktop Maps Fields Between Siebel CRM Data and IBM Notes Data >

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

Table 36 describes how Siebel CRM Desktop maps objects between a Siebel CRM activity and IBM Notes Calendar.

Table 36. How Siebel CRM Desktop Maps Fields Between Siebel Activities 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 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 CRM Desktop resolves the primary email of the employees.

No

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

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 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 CRM Desktop creates a mapping error.

The IBM Notes activity includes another field to store the Priority value that 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 CRM Desktop validates the stored value.
  • If the value that is stored for the activity is ASAP, then CRM Desktop uses the ASAP value from the activity.
  • If the value that is stored for the activity is not ASAP, then CRM Desktop uses the value from the IBM Notes record.
      
Siebel CRM Desktop for IBM Notes Administration Guide Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.