1. Configuring Siebel Open UI Guide
  2. Life Cycle of a Physical Renderer

Life Cycle of a Physical Renderer

The following figure illustrates the life cycle of a physical renderer. For examples of various life cycle flows, see Life Cycle Flows of User Interface Elements.

Life Cycle of a Physical Renderer: This image is described in the surrounding text.

As shown in this figure, the physical renderer uses methods in the following sequence:

  1. Renderer. Creates the renderer.

  2. Init. Initializes and sets up the AttachPMBinding method. For more information, see Init Method.

  3. The Open UI framework makes a call to the context renderer's Init function after instantiating it. Siebel Open UI adds the corresponding physical renderer's instance to this function and the implementation can use the physical renderer or presentation model's interface.

  4. ShowUI. Displays a physical control that corresponds to an applet control. It renders the container for the metadata, data, and event bindings. For example, when Siebel Open UI renders a list applet as a grid, ShowUI renders the third-party grid control that it uses for the applet. Also, ShowUI calls all of the plug-in wrappers of the associated applet controls. For more information, see ShowUI Method.

  5. BindEvents. Sets up the user interface binding of events to the physical user interface, represented as HTML elements. It captures the user actions, and then translates these actions to logical events in the physical renderer before Siebel Open UI sends them to the presentation model for processing. Also, BindEvents calls all of the plug-in wrappers of the associated applet controls. For more information, see BindEvents Method.

  6. BindData. Downloads metadata and data from the Siebel Server to the client proxy, and then binds this data to the user interface. The list columns that a list applet uses is an example of metadata, and the record set that this list applet uses is an example of data. Also, BindData calls all of the plug-in wrappers of the associated applet controls. For more information, see BindData Method.

  7. The context renderer's Execute method is called by the framework immediately after the physical renderer's lifeCycle method execution, that is, after the ShowUI, BindData, BindEvents functions. OpenUI also adds the corresponding physical renderer's instance to this function and the implementation can use the physical renderer or presentation model's interface.

  8. AttachPMBinding. Attaches handlers to notifications that occur during the life cycle. For more information, see AttachPMBinding Method. For more information about notifications that can occur during the life cycle, see Notifications That Siebel Open UI Supports.

    GetPM. Calls a method that the presentation model contains. It is recommended that you use GetPM only to call the following presentation model methods:

    • ExecuteMethod

    • OnControlEvent

    • Get

    • SetProperty

    You can use ExecuteMethod or OnControlEvent to call a method that modifies the state of the presentation model or to call a method that reads this state. You can use the Get method to get the value of a presentation model property. You can use SetProperty to set the value of a presentation model property.

    For more information, see GetPM Method for Physical Renderers and OnControlEvent Method.

  9. EndLife. Ends the life of the physical renderer. For more information, see EndLife Method.