Integration Objects That Siebel CRM Desktop Uses

Siebel CRM Desktop uses integration objects that include the following prefix:

CRMDesktop

You must not create a new integration object for an existing object. Only create a new integration object for a new, custom object that does not already have an integration object. Consider the following examples:

• You must not create a new integration object for accounts. Instead, you can extend the CRMDesktopAccountIO integration object.

• You must create a new integration object for Channel Partner. For more information, see Creating an Integration Component for the Channel Partner MVG.

The following list includes some of the integration objects that allow Siebel CRM Desktop to access Siebel CRM data, such as accounts, opportunities, and contacts. Note that this list includes only some integration objects. It does not include all the integration objects that Siebel CRM Desktop uses:

• CRMDesktopAccountIO

• RMDesktopActionI

• CRMDesktopAssignmentGroupI

• CRMDesktopBusinessAddressI

• RMDesktopContactI

• CRMDesktopCurrencyI

• RMDesktopEmployeeI

• RMDesktopIndustryI

• RMDesktopInternalDivisionI

• CRMDesktopInternalProductIO

• RMDesktopListOfValuesI

• RMDesktopOpportunityI

• RMDesktopPickListGenericI

• RMDesktopPickListHierarchicalI

• RMDesktopPositionI

• RMDesktopSalesCycleDefI

• RMDesktopSystemPreferencesI

• RMDesktopUserDetailsI

Siebel CRM Desktop uses the following integration objects to meet other integration requirements:

• CRMDesktopLocaleIO. PIM locale setting integration objects that provide access to the locale settings.

• CRMDesktopSystemPreferencesIO. An integration object for a PIM system preference that provides access to the system preferences for the Siebel Server.

• CRMDesktopUserDetailsIO. For login user data.

• PIMClientMetaData and PIMClientMetadataFile. For metadata file download.

• PIMClientSync. A wrapper that includes other integration objects.