Siebel Developer's Reference > Siebel Templates for Employee Applications > Overview of Configuring Siebel Templates for Employee Applications >

Guidelines for Configuring Applet Templates

If you configure an applet template, then use the following guidelines:

• Never map a native HTML button to a list or form. You can set the properties for a MiniButton the same way you set the properties for most controls.
• To save time during configuration, you can place the button divider after the menu button and before the previous record button.
• To maximize the potential for vertical alignment, place taller fields, such as text area fields, at the bottom of the form. Siebel CRM displays each column of fields independently of the other columns. This configuration maximizes form layout options and minimizes gaps that might occur between fields in the same column but where the alignment of fields across columns might not remain vertical.
• To define the text that Siebel CRM displays in the client, you can map the control on a label and use the Caption property of the control. A form section is not a control. It is a label that groups related fields. The FormSection control implements a form section. Siebel CRM expands the FormSection label to fit the region where you place it. To set it apart from the background color, the label displays against the FormSection color that the cascading style sheet defines. For more information about this control, see Configuring Siebel Business Applications.
• If you configured Siebel CRM in an earlier version to use the Previous or Next text labels, then you must reconfigure this customization to use the RecNavPrv and RecNavNxt controls. All record navigation must map to these controls. For more information about these controls, see Configuring Siebel Business Applications.