Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Developer's Reference > Siebel Templates for Employee Applications > Form Templates > Overview of Using Applet Form TemplatesThis topic describes an overview of using applet form templates. About Form Layouts That Use a GridA grid layout template does not use placeholder tags. It uses the following Siebel tags in a single location for all controls that reside in the main body of the form: swe:form-applet-layout A grid layout template includes the following items:
An applet Web template that uses a grid is different from an applet Web template that does not use a grid in the following ways:
For examples of grid layout templates, see Grid Layout Form Template and Popup Form, Grid Layout Template. About Form Layouts That Do Not Use a GridThis topic describes form layouts that do not use a grid that are available but that no longer come predefined with Siebel CRM. Siebel CRM versions before version 7.7 use form applets that do not use a grid in Edit mode in standard interactivity mode. Starting with Siebel CRM version 7.7, most form applets use a grid layout. The four column form templates define a set of layout regions. A region can include one or more label and field pairs. You can use Siebel Tools to place a control in a region and to resize the control. The four column form includes regions that are different in height. It can accommodate controls that span one, two, or four columns. Siebel CRM groups these regions. This grouping helps make sure that each region uses only the minimum vertical space that Siebel CRM requires to display it. If Siebel CRM does not map any control to a region, then it collapses this region and moves the next region up in the form. To create a wide variety of form designs while maintaining only one form template, you can combine horizontally proportioned regions with grouped regions. Figure 1 displays the master template for layout regions. Figure 2 includes an example of a layout that Siebel CRM creates from the master template. Each X indicates a region that does not contain any mapped control. Figure 3 includes another example of a layout that Siebel CRM creates from the master template. How Siebel CRM Maps Controls for Forms That Do Not Use a GridFigure 4 displays the ID ranges that Siebel CRM uses for the controls that it displays in each region. It is recommended that you configure Siebel CRM to map each control to the lowest ID that is available in each region. About the Style That Some Four Column Form Templates UseThe following templates create the same layout for a form that includes four columns. They also support child and grandchild styles.
Figure 5 includes a parent style that these templates display. Figure 6 includes a child style that these templates display. Capabilities of Four Column Form TemplatesForm templates that include four columns can do the following:
|
![]() ![]() |
Siebel Developer's Reference | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |