- More elements for composition of the user interface.
For more information, see the description of the Type field in Added Fields in Siebel Composer.
- More efficient rendering of Web pages.
The DOM (Document Object Model) structure in Siebel Business Applications is simplified, and the DOM is assembled using a single HTTP response, not multiple relays between the client and the server. For more information, see Aspects of Responsive Web Design in Siebel Composer.
When you use Siebel Tools, content is trimmed only from the client. Also, post-response JavaScript execution trims content. When you use Siebel Composer, the server evaluates client capabilities, such as resolution and form factors. Content is tailored from the server, and more efficient options are available to manage content.
- Expanded options for generating content.
You can specify standard Siebel expressions for additional elements in the user interface, such as Web templates, Web pages, and views. For more information, see the description of the Expression field in Added Fields in Siebel Composer.
- Expanded options for styling content.
You can designate classes for the CSS (Cascading Style Sheet) in a DOM with valid IDs to configure the styling of a Siebel application. A DOM without valid IDs is removed from the server. For more information, see the description of the HTML Attributes field in Added Fields in Siebel Composer.
Tables related to the layout of the user interface are removed.
- Decreased network traffic.
Only the content that is necessary to currently render the user interface is included in responses. Extraneous content that the client must later discard or ignore is not included in responses. This decrease in content decreases the network traffic.
- No downtime during configuration deployment.
When you use Siebel Tools to configure a Siebel application or a Siebel Web template, you must restart the application server to deploy the updated SRF (Siebel Repository File) into the production environment. When you use Siebel Composer for this configuration, you just log in to the application again to view the deployed configuration. For more information, see About Compiling and Publishing.
- More control in the client.
In addition to existing stubs for the presentation model and physical renderer in applets and views, stubs for the presentation model and physical renderer are available for Web pages. Consequently, the Siebel Configurator can use the presentation model of a Web page to alter its properties and behavior, and the Siebel Configurator can use the physical renderer of a Web page to change its rendering.
- Improved file loading.
The framework files that are needed to start a Siebel application are loaded from the manifest. The files for the presentation model and physical renderer that are needed to render Web pages are also loaded from the manifest.
