Overview of How Siebel CRM Uses Siebel Tags

Siebel CRM maps a Siebel object to an Id in a web template. The Siebel web templates do not include references to controls in the Siebel repository. Instead, they include placeholder tags that define layout and style. The following is an example of a Siebel tag that places a web page item in a web page:

<div od-type="control" id="1" property="FormattedHtml"/>

Other Siebel tags place other items in a web page, such as view bars, applets, or controls.

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

  1. For the current web page, it examines the Siebel runtime repository for web page item whose Item Identifier property is equal to 1. This is the mapping between the template file object and the repository object. For more information about the item identifier, see Properties of the Applet Web Template Item.

  2. To replace the placeholder in the template file, it displays the Formatted HTML representation of this repository object.

The following image shows how the mapping between controls and IDs work to display an image as a link to add a new contact. In this image:

  • The SWT File for the Applet is as follows:

    ...
    <div od-type="control" id id="1" property="FormattedHtml">
       <img src="images/new_contact.gif" width="14" height="14">
    <!--od tag control close-->
    </div>
    ...
  • Control 1 in the Siebel Repository has the following properties:

    Method: New Record

    Type: Link

  • The HTML output on the Siebel Server is as follows:

    ...
    <a href-"start.swe?sweCmd=NewRecord> 
       <img src="images/new_contact.gif" width="14" height="14">
    </a>
    ...

The HREF is likely different in your implementation. If you create the correct controls and template mappings, then the Siebel Web Engine creates a URL in the HREF that runs the NewRecord method in the correct context.

Example of Mappings Between Controls and IDs: This image is described in the surrounding text.