Siebel CRM Desktop for IBM Notes Administration Guide > Customizing Siebel CRM Desktop > Customizing Field Behavior >

Displaying Siebel CRM Fields

The example in this topic displays the Mail Stop field on the Contact form in the client. You make this field available through the Siebel API and then customize CRM Desktop to synchronize and display the field. You modify the following files:

• siebel_meta_info.xml
• Ln_siebel_basic_mapping.xml
• Ln_package_res.xml
• (SBL)\CRMContactSubform.version8 subform design element

For more information, see Files in the Customization Package.

To display a Siebel CRM field

1. Open Siebel Tools and then display the object type named Integration Object.

   For more information, see Displaying Object Types in Siebel Tools.

2. Make sure the Mail Stop field exists on the Contact business component.

   If it does not, then add it now.

3. Add the Mail Stop field to the CRMDesktopContactIO integration object.

   In order for CRM Desktop to synchronize data with the Siebel database, you use CRM Desktop integration objects and integration components to make the objects and fields that you use in this example available. The Contact object is already available but the Mail Stop field is not. To make the Mail Stop field available, you add it to the Contact integration component for each of the required integration objects:

   1. In the Object Explorer, click Integration Object and then locate the CRMDesktopContactIO integration object in the Integration Objects list.
   2. In the Object Explorer, expand the Integration Object tree, click Integration Component, and then locate the Contact integration component in the Integration Components list.
   3. In the Object Explorer, expand the Integration Component tree and then click Integration Component Field.
   4. In the Integration Component Fields list, add a new record using values from the following table.

      Property	Value
      Name	Mail Stop
      Data Type	DTYPE_TEXT

4. Repeat Step 3 for the CRMDesktopAccountIO integration object.
5. Repeat Step 3 for the CRMDesktopOpportunityIO integration object.
6. Compile all locked projects.

   After compiling finishes, the Mail Stop field is available through the API and you can configure CRM Desktop to use the field. For more information, see Using Siebel Tools.

7. Specify the objects and fields to synchronize:
   1. Use an XML editor to open the siebel_meta_info.xml file.

      For more information, see Files in the Customization Package.

   2. Locate the following tag:

   object TypeId='Contact'

   Several child field tags reside in the object TypeId='Contact' tag. These children identify the fields for the Contact object.

   3. Add the following field tag as a child of the tag that you located in Step b:

   <field Name='Mail Stop' Label='Mail Stop' DataType='DTYPE_TEXT' IOElemName='MailStop' />

   4. Repeat Step b and Step c for the following tag:

   object TypeId='Account.Contact'

   5. Repeat Step b and Step c for the following tag:

   object TypeId='Opportunity.Contact'

   6. Save and close the siebel_meta_info.xml file.
8. Map the Mail Stop field from the Contact object in the Siebel database to a field in CRM Desktop:
   1. Use an XML editor to open the Ln_siebel_basic_mapping.xml file.

      For more information, see Files in the Customization Package.

   2. In the Ln_siebel_basic_mapping.xml file, add a new field tag to the type tag using values from the following table.

      Tag	Value
      type id	Contact

   3. Add the following code to the tag you created in Step b.

   <field id="Mail Stop">
     <reader>
       <lotus_std>
         <lotus_field id="MailStop"/>
         <convertor>
         <string/>
         </convertor>
       </lotus_std>
     </reader>
     <writer>
       <lotus_std>
         <lotus_field id="MailStop"/>
         <convertor>
         <string/>
         </convertor>
       <lotus_std>
     </writer>
   </field>

   4. Save and close the Ln_siebel_basic_mapping.xml file.
9. Insert a label and the Mail Stop field just following the Job Title field on the Contact form:
   1. Open IBM Domino Designer, locate, and then open one of the following forms:
      • Contact.version7 form for IBM Notes version 7
      • Contact.version8 form for IBM Notes version 8

        This example describes how to modify the Contact.version8 design element. For more information, see Opening IBM Domino Designer.

   2. Add the Mail Stop text field.

      In IBM Domino Designer you must add one cell for the label and one cell for the field. In the label cell, you must add the localization macro. You use the following localization macro for this example:

   (!loc:lb_mail_stop:loc!):

   where:

   • (!loc. Is the beginning of the macro.
   • lb-mail_stop. Is the unique Id for the field.
   • loc!):. Is the end of the macro.
   • lbl_mail_stop. Specifies the key that the Ln_package_res.xml file uses to determine the localized value for the label.
   3. Set the name of the field cell that you added in Step b to MailStop.
10. Add the following code to the Ln_package_res.xml file:

    <str key="lbl_mail_stop">Mail stop:</str>

    Add this code as a child of the res_root tag under the following comment:

    <!-- Contact CRMD -->

    This code provides localized valuesto the client. It allows the Contact form to display the Mail Stop label through a key value. The Ln_package_res.xml file provides localized values and images to CRM Desktop. You added the new Mail Stop field to the Contact form, so you must provide the text for the label. When you modified the Contact.version7 or Contact.version8 form, you created text that contains bl_mail_stopfor the text value. This text value identifies the key to use in the Ln_package_res.xml file.

11. Republish the updated package files.

    During the next synchronization, CRM Desktop uses the updated files to apply the modifications to the Contact form. The Mail Stop field is available on the Contact form and CRM Desktop synchronizes the values in this field with the Siebel Server. For more information, see Republishing Customization Packages.