Configuring Siebel Open UI > Customizing Siebel Open UI > Guidelines for Customizing Siebel Open UI >

Guidelines for Customizing Physical Renderers

It is recommended that you apply the following guidelines if you configure a physical renderer:

• Use a physical renderer only to implement methods that render the presentation model state:
  • Do not include any other logic in a physical renderer.
  • Do not include business logic that modifies the user interface state.
  • Only use a physical renderer to send user action events to the presentation model, and use the presentation model to do all the work that is necessary to modify a state.
  • Allow the physical renderer to rebind the new presentation model state to the rendered user interface only after the presentation model finishes modifying the state of the logical user interface.
• Do not use a physical renderer to add any presentation attributes to the Document Object Model (DOM). Example attributes include position, color, or any other styling. To modify a presentation attribute, you must attach or detach a style that you define in a CSS file.
• Configure Siebel Open UI to do all rendering only in a physical renderer. It is strongly recommended that you do not configure Siebel Open UI to do direct DOM manipulation. If you cannot avoid direct DOM manipulation, then you must do this manipulation in a physical renderer. Configure Siebel Open UI to send data, metadata, or state information to controls only from a physical renderer. For more information, see About Objects and Metadata.
• In most situations, if you add a presentation model, then you must also add a corresponding physical renderer. You typically use a presentation model to add custom logic in the client. This logic typically determines a physical behavior that requires a physical renderer to do the rendering. For example, in most situations, you cannot configure a predefined applet that also renders custom logic. Siebel Open UI structures custom JavaScript logic in the presentation model and physical renderer as a customization of predefined Siebel Open UI. This structure allows Siebel Open UI to use Oracle JavaScript and to use other logic that a predefined Siebel Open UI provides, such as events, Siebel arrays, and so on. It is not recommended that you configure JavaScript that is independent of Siebel Open UI, and that also modifies Siebel CRM data or physical behavior.