Siebel CRM Desktop for Microsoft Outlook Administration Guide > XML Files Reference > XML Code That Customizes Forms >

Control Tag of the Forms File

The control tag defines a control that is located in a cell. It includes the following attributes:

• id. Defines the control ID. If you use the id attribute to specify the ID of a native Microsoft Outlook control, then Siebel CRM Desktop requires no more attributes except tab_order, if necessary. The class attribute defines the control type.
• tab_order. Defines the tab order of the control. CRM Desktop displays the control that contains the smallest tab_order value as the first control in the tab order. You can start at 1. If the control contains no tab_order, then CRM Desktop does not include the control in the tab order. For more information, see Making Sure Tab Order Is Unique.
• class. Defines the type of the control. Depending on the value of the class attribute, you must specify more attributes and tags. For more information, see Types of Controls for the Control Tag of the Forms File.
• allow_negative. For multi_currency control only.
• caption. For list control only.
• type. For Microsoft Outlook_view control only.
• view_id. For Microsoft Outlook_view control only.

The following controls support the control tag:

• button
• check box
• gradient_checkbox

The control tag includes the following tags. These tags depend on the value that the class attribute of the parent control tag contains:

• source. Used for multivalue controls, such as dropdown list, lookup, and mvg_primary_selector. It defines the objects that CRM Desktop displays in this control. It includes the following attributes:
  • type. Defines the object type that CRM Desktop displays in the current control. The basic_mapping.xml file must describe this object type.
  • display_format. Defines the object fields that CRM Desktop displays in a control. Used only for the mvg_primary_selector control.
  • format. The same as the display_format tag, but applied to other controls.
  • field. Defines the object field that CRM Desktop displays as chosen in a dropdown list. Used only for the dropdown list control.
  • left_id. Defines a field on a related object where CRM Desktop stores the ID of the parent object. CRM Desktop uses the left_id control on this parent object ID. It uses it only for the mvg_primary_selector control.
  • item_value. Defines a field on a related object where CRM Desktop stores the ID of the parent object. This is the ID of the chosen object. It is used only for the mvg_primary_selector control.
• text. Defines the text that CRM Desktop uses for the control. You use this tag primarily for the label control.
• field. Contains the field identifier that this control uses:
  • The siebel_basic_mapping.xml file must describe this field tag.
  • Contains the value attribute. CRM Desktop uses this attribute only for edit controls. This attribute describes the value type for the field.
  • The following values are available: string, binary, int, double, or currency.
  • The API name field is an example of a field identifier.

Example Code of the Control Tag

The following code is an example of the control tag:

<cell>
  <control id="0x10000" class="edit">
    <field value="string"> Name</field>
  </control>
</cell>

Making Sure Tab Order Is Unique

Make sure that the tab order is unique through the entire form. For example, if you add a field to the Contact form, then adjust the tab_order values for the tab_orders that this form uses. For example, if the tab_order value is 15, then you must set it to 17. You increment it by a value of one for the label and one for the field. This configuration makes sure the user can correctly tab through the form.