Configuring Siebel Open UI > Architecture of Siebel Open UI > Life Cycle of User Interface Elements >

Life Cycle of a Physical Renderer


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

Figure 15. Life Cycle of a Physical Renderer
Explanation of Callouts

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. 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.
  4. 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.
  5. 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.
  6. 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.

  1. EndLife. Ends the life of the physical renderer. For more information, see EndLife Method.
Life Cycle of a Plug-in Wrapper

The plug-in wrapper uses methods in the following sequence:

  1. ShowUI. Performs show related activities for a control. For more information see ShowUI Method.
  2. BindEvents. Attaches events to the DOM instance of the control. For more information see BindEvents Method.
  3. BindData. Initializes data to the DOM instance of the control. For more information see BindData Method.
  4. EndLife. Ends the life of the Plug-in Wrapper. For more information see EndLife Method.
Configuring Siebel Open UI Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.