Siebel Server Sync Guide > Setting Up and Using Siebel Outlook Add-In > Process of Configuring Custom Objects in Siebel Outlook Add-In >
Updating Integration Objects
This topic describes how to update the PIMSI Integration Object and the PIMSI Intermediate Integration object that SSSE uses for synchronization. Updating these objects allows the PIMSI server components to correctly synchronize data after a user has selected the Siebel object that you have made available in the Siebel Outlook Add-In. You must update the integration objects of the domain associated with the Microsoft Outlook record. For example, if you are configuring the Siebel Outlook Add-In to link Microsoft Outlook contact records with Siebel Household records, then the two Integration Objects that you must update are the PIMSI Business Contact and the PIMSI Intermediate Business Contact integration objects. This task is a step in Process of Configuring Custom Objects in Siebel Outlook Add-In. NOTE: When performing the procedures in this topic, replace Household with the name of the Siebel object you are adding to the Siebel Outlook Add-In, and Contact with the name of the Microsoft Outlook object you want to link to the new Siebel object.
The following procedure describes how to update the PIMSI Integration Object. To update the PIMSI Integration object
- In Siebel Tools, query for the relevant Integration Object for the domain being updated, in this example, PIMSI Business Contact.
- Create a new Integration Component, or activate an existing component, specifying values similar to those shown in the following table.
NOTE: In this table, italics indicate that you are supposed to substitute some other value for the value in the field. Values in the table that are not in italics must be entered literally.
For information on creating and activating Integration Objects, see Integration Platform Technologies: Siebel Enterprise Application Integration.
|
|
|
External Name Context |
Contact_Household |
Specify ParentObjectName_New AddInObject |
Name |
Contact_Household |
Specify the value chosen for the External Name Context attribute. |
Parent Integration Component |
Contact |
The name of the parent Integration Object. |
External Name |
Household |
The name of the Siebel object you are adding to Outlook Add-In. |
External Sequence |
6 |
Specify the next available sequence number. |
Cardinality |
Zero or More |
Because Household is not a required field, you can specify either Zero or More for the Cardinality attribute. |
XML Container Element |
ListOfContact_Household |
Specify ListOfNameAttributeValue |
XML Sequence |
10,006 |
10,000 plus the External Sequence number specified. |
- Select the Contact_Household Integration Component, then add a record to the Integration Component User Props applet to indicate that the child (Household) object is to be treated as an MVG.
- Create Integration Component Fields for system fields, and for any field that you want to make available in the Outlook Add-in, using values similar to those shown in the following table.
NOTE: You must create the first three fields shown in the following table.
|
|
|
|
|
Name |
Household Id |
IsPrimaryMVG |
operation |
Households |
Data Type |
DTYPE_ID |
DTYPE_TEXT |
DTYPE_TEXT |
DTYPE_TEXT |
Len |
30 |
1 |
30 |
100 |
Type |
Data |
System |
System |
Data |
Ext. Name |
Household Id |
IsPrimaryMVG |
operation |
Household Name |
Ext. Data Type |
|
|
|
DTYPE_TEXT |
Ext. Length |
|
|
|
100 |
Ext. Seq. |
1 |
2 |
3 |
4 |
XML Seq. |
1 |
2 |
3 |
4 |
XML Style |
Element |
Attribute |
Attribute |
Element |
- For the Household Name Integration Component field, specify the following user property to indicate that the name of the field in the child business component (in this example, Household) is different to the name in the parent business component (in this example, Contact).
|
|
AssocFieldName |
Household Name |
- For the Household Id Integration Component field, specify the following Integration Component Field user property to indicate that name of the field in the child business component (in this example, Household) is different to the name in the parent business component (in this example, Contact).
- Create Integration Component Keys using values similar to those shown in the following table.
|
|
|
Status Key |
|
Status Key |
User Key:1 |
1 |
User Key |
- For the Status Key Integration Component Key, add the following Integration Component Key fields, using values similar to those shown in the table.
|
|
Id |
Household Id |
Operation |
operation |
- For the User Key: 1 Integration Component Key, add the following Integration Component Key fields, using values similar to those shown in the table.
|
|
Household Name |
Household Name |
The following procedure describes how to update the PIMSI Intermediate Integration Object. To update the PIMSI Intermediate Integration object
- In Siebel Tools, query for the relevant Intermediate Integration Object for the domain being updated, in this example, PIMSI Intermediate Business Contact.
- Create a new Integration Component specifying values similar to those shown in the following table.
For information on creating and activating Integration Objects, see Integration Platform Technologies: Siebel Enterprise Application Integration.
|
|
|
External Name Context |
HouseholdInfo |
Specify AddInObjectNameInfo. |
Name |
HouseholdInfo |
Specify the value chosen for the External Name Context attribute. |
Parent Integration Component |
BusinessContact |
The name of the parent Integration Object. |
External Name |
HouseholdInfo |
Specify AddInObjectNameInfo. |
External Sequence |
1 |
This value must be set to 1. |
Cardinality |
One or More |
This value must always be set to One or More. |
XML Container Element |
ListOfHouseholdInfo |
Specify ListOfNameAttributeValue |
XML Sequence |
1 |
This value must always be set to 1. |
- Create Integration Component fields for system fields, and for any field that is to be displayed in the Outlook Add-in, using values similar to those shown in the following table.
NOTE: You must create the two fields shown in the following table, and can create additional fields as required.
|
|
|
Name |
HouseholdId |
HouseholdName |
Data Type |
DTYPE_TEXT |
DTYPE_TEXT |
Len |
Not applicable |
Not applicable |
Type |
Data |
Data |
Ext. Name |
HouseholdId |
HouseholdName |
Ext. Seq. |
1 |
2 |
XML Seq. |
1 |
2 |
XML Style |
Element |
Element |
When you have modified the PIMSI Integration Objects, compile the modified integration objects to generate a new Runtime Repository, then stop the Siebel Server, deploy the new Runtime Repository, and then restart the Siebel Server.
|