Siebel Tools Reference > Physical User Interface Layer > Understanding Siebel Tags >

Mappings Between Controls and IDs

The .SWT template files do not include references to specific controls in the repository. Instead, they specify a layout and style, with placeholder tags. The following is an example of a Siebel tag that places a Web Page Item in a Web Page. Other Siebel tags might place other items, such as view bars, applets, or controls, for instance, in a Web Page.

<swe:Control id="1" property="FormattedHtml"/>

To process this tag and generate the final HTML the Siebel Web Engine does the following:

  1. Examines the compiled .srf file for the properties of the Web Page Item in the current Web Page that has an Item Identifier equal to 1. This is the mapping between the template file object and repository object.
  2. Renders the Formatted HTML representation of this repository object in place of the abstract placeholder in the template file.

Figure 220 shows how the mappings between controls and IDs work for displaying an image as a link to add a new contact. The example illustrates the general point, but note that in your actual implementation, the HREF probably will not look exactly like this. If you create the right controls and template mappings, Siebel Web Engine will construct a URL in the HREF that will execute the method NewRecord in the correct context.

Figure 220.  Mappings Between Controls and IDs

 Siebel Tools Reference
 Published: 20 October 2003