Bookshelf Home | Contents | Index | PDF |
Configuring Siebel Business Applications > About Siebel Web Templates and Siebel Tags > Guidelines for Configuring Siebel Web Templates and Siebel TagsThis topic describes guidelines for configuring Siebel web templates and Siebel tags. Guidelines for Naming a Siebel Web TemplateThe file name of a Siebel Web template uses the SWT extension. For example, CCPageContainer.swt, CCHomePageView.swt, and so forth. You are not required to use this format. The Siebel Web Engine recognizes and interprets the file correctly regardless of how you name it. However, it is recommended that you use swt for the file extension to help develop and maintain Siebel CRM. The swt extension provides you with a way to immediately recognize how Siebel CRM uses the file. Siebel CRM typically stores Siebel Web template files in the Web Template directory in your Tools installation directory. The Filename property references the Web Template object type. Guidelines for Using Modes with Web TemplatesIn many situations, it is not necessary to use Base mode forms, which are read-only. You can use persistently editable forms because tasks often include data editing and input. This type of form improves usability because the user can enter data without having to click an edit button, and then wait for Siebel CRM to display the form in edit mode. If an applet is in Edit mode in a view, as defined by the applet mode property of the view web template item, then Siebel CRM never displays this applet in Base mode. If the user updates the field values in this applet and then commits the change, then Siebel CRM continues to display the applet in this mode after Siebel CRM writes the changes to the Siebel database. To display an applet in Query or New mode, you can call a method, such as NewQuery or NewRecord, on an applet that Siebel CRM displays in Edit mode. After Siebel CRM executes the query or writes the new record, Siebel CRM displays the applet in Edit mode. For more information, see Options to Control How the User Creates, Edits, Queries, and Deletes CRM Data. Guidelines for Using HTML Frames in a View Web TemplateIf you use HTML frames in a view web template, then use the following guidelines:
Guidelines for Creating HTML Frames in a Container PageSiebel CRM uses the container page template to create the frame definition document for the Siebel application. If you define HTML frames in a container page, then use the following guidelines:
Guidelines for Using Cascading Style SheetsA cascading style defines qualities of user interface elements, such as color schemes and fonts. The following examples describe how you can use a cascading style sheet to modify the look and feel of the Siebel client:
Although you can configure Siebel web templates to use format tags, if you store style information in cascading style sheets rather than in Siebel web templates, then you can realize the following benefits:
Because Siebel CRM renders style information that is stored in a cascading style sheet slightly differently in different browsers, you must test your configuration in all browsers that your users use. Cascading style sheet files are located in the following directories:
NOTE: If you apply a patch, then Siebel CRM might overwrite the CSS files. If this happens, then you must manually reenter the modifications you made to the cascading style sheets. For more information, see Cascading Style Sheet and Siebel Developer's Reference. Guidelines for Modifying a Predefined QueryIf you modify a predefined query, then use the following guidelines:
Consider the following requirements for standard interactivity and high interactivity:
For more information, see About Standard Interactivity and High Interactivity. Query Management CommandsA user can add a named query in the combo box. Siebel CRM accomplishes this through the query management commands that are available as invoke method calls through the class of the base applet. Siebel CRM makes these queries available to the user as menu items or toolbar buttons. Siebel CRM supports the following commands:
NOTE: It is strongly recommended that you do not define an Edit button for the predefined query feature. Because the Edit button must call the Refine method, problems can arise if an Edit button exists in a multiview environment and there is no way to determine the active view. |
Configuring Siebel Business Applications | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |