|Bookshelf Home | Contents | Index | PDF|
A Siebel web template includes a preset format that Siebel CRM reuses each time Siebel CRM requires a particular layout. This way, Siebel CRM uses only a single template rather than multiple files every time it requires a particular layout. For more information, see Siebel Web Template.
A Web browser uses HTML to define the layout and format of a page. Siebel web templates provide this HTML layout to the Siebel Web Engine when Siebel CRM renders Siebel objects in the Siebel client. The templates contain markup tags, such as HTML, WML, and XML, that are interspersed with Siebel tags. Siebel CRM prefixes these tags with the following text: swe.
A Siebel web template includes empty placeholders that contain no data. To enter data and user interface elements into a template, Siebel CRM associates views, applets, controls, and other objects with each template. These objects are defined in the Siebel repository. Siebel CRM maps each object to an empty placeholder in the template. For example, assume a view maps to three applets. You associate a view web template with the view, and then map each applet to a placeholder in that template.
Siebel CRM renders a wireless application in the same way as it renders an application that is not wireless except for the fact that the markup language in the templates uses WML or XML code. Although this topic describes configuration for Web (HTML) applications, many of the concepts described in this chapter are generic across markup languages.
Figure 30 illustrates the development environment you use to generate HTML output. The Siebel Web Engine uses templates, repository definitions, and HTML to generate HTML output.
You can share a Siebel Web template among many objects in the Siebel repository. Because a template includes placeholders that do not contain data, Siebel CRM can map any number of repository objects to a specific placeholder. This allows you to change only one template to apply style or structural changes to numerous user interface elements. A typical Siebel application contains approximately 5 to 50 templates. These templates form the basis for several hundred views and applets. For example, Siebel CRM can share a template that defines the layout and format of a predefined list applet among all list applet definitions in the Siebel repository.
If a placeholder is not mapped, then the Siebel Web Engine ignores it and the HTML between the Siebel tags that define the placeholder. For example, if the template contains layout for a list applet that is 10 columns in width but only two of the columns are mapped, then the Siebel Web Engine ignores the other eight unmapped columns. This technique improves efficiency and performance.
Siebel CRM comes with many predefined applet web templates and view web templates that you can modify. To support your business processes, it might not be necessary for you to modify any of the applet web template and view web templates. However, in some situations, especially with customer and partner applications, you can modify predefined templates to reflect your corporate look and feel. You can also create entirely new templates.
A Siebel Web template file can include another Siebel Web template. Siebel CRM uses this technique to improve efficiency. For example, to separate handling for the title of an applet from handling the body of an applet, you can create a template file that includes the title in the applet template. This way, you can define an applet layout once and then combine it with multiple different title layouts.
The layout and style of HTML Web pages is dynamic, which allows simultaneous support for multiple browser types and versions. A Siebel web template supports conditional branching. Siebel CRM evaluates conditions according to the results of a business service.
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|