About Customizing SSSE

SSSE supports the following kinds of customization within each supported domain and for a specified set of database tables:

• Modifying certain properties of fields that are already available for synchronization, such as field names

• Modifying existing field mappings in the following ways:

  • Mapping a Microsoft Exchange field that is already synchronized with a Siebel field that you add for synchronization.

  • Mapping a Siebel field or multi-value group (MVG) that is already synchronized with a Microsoft Exchange field that you add for synchronization.

• Adding new field mappings in the following ways:

  • Adding a new field or MVG for synchronization in a supported Siebel business component and mapping it to a previously unmapped Microsoft Exchange field (includes adding a new column in the underlying Siebel base table).

  • Adding a new field for synchronization in Microsoft Exchange and mapping it to a previously unmapped Siebel field or MVG.

• Deleting existing field mappings.

• Changing the delta queries that SSSE uses to find changed Siebel data that is to be synchronized for a particular user.

• Creating custom delete triggers that direct SSSE to delete PIM records. This capability supports actions such as converting a record from one domain to another.

The customization process can involve changing some or all of the following entities:

• Integration Objects

• Integration Data Maps

• Domain configurations

• Field configurations

• Delta Query profile

• Delete triggers

Any administrator who customizesSSSE requires experience with working with the Siebel Repository, and a good working knowledge of Microsoft Exchange, including the internal representations of field names in Microsoft Exchange.