Configuring Siebel Open UI > Architecture of Siebel Open UI > About the Siebel Open UI Development Architecture >

Example of How Siebel Open UI Renders a View or Applet

Figure 2 illustrates how Siebel Open UI renders the Contact Form Applet.

Figure 2. Example of How Siebel Open UI Renders a View or Applet

Explanation of Callouts

Siebel Open UI does the following to render the Contact Form Applet:

1. The user attempts to navigate to the Contact Form Applet.
2. Siebel Open UI creates the view that displays this applet. This creation is similar to how Siebel CRM creates a view in high-interactivity mode.
3. To identify the rendering key, Siebel Open UI references the user properties of the Contact Form Applet, or it references a custom entry that you add in the manifest_extensions.map file. For more information, see About the Rendering Key.
4. Siebel Open UI uses the rendering key it identified in Step 3 to identify the JavaScript files it must use to render the Contact Form Applet. The Manifest File includes this rendering key. For more information, see How Siebel Open UI Identifies the JavaScript Files It Requires to Render a View or Applet.
5. Siebel Open UI downloads the JavaScript files it identified in Step 4 to the client.
6. A presentation model formats the data and applies application logic. For more information, see Example of a Presentation Model.
7. A physical renderer registers itself with the mapping for each rendering key value to a corresponding object. It does this in a table that the Client Framework maintains in memory. The Client Framework uses the applet user properties of the Contact Form Applet when it examines this table to determine the JavaScript class it must use for this applet. A presentation model also does this registration for each rendering key value that it uses. For more information, see Example of a Physical Renderer.
8. Siebel Open UI loads the cascading style sheets according to entries that the theme.js file contains.
9. Siebel Open UI uses a presentation model, physical renderer, and cascading style sheets to render the Contact Form Applet.

Example of a Presentation Model

Figure 1 describes how the partialrefreshpm.js file does a partial refresh for a presentation model. It is recommended that you include this business logic in a presentation model so that multiple modelers can reuse it. To get a copy of this file, see Article ID 1494998.1 on My Oracle Support. To view an example that uses this file, see Configuring Siebel Open UI to Partially Refresh Web Pages Without Calling the Siebel Server.

Figure 3. Example of a Presentation Model

Explanation of Callouts

The partialrefreshpm.js file includes the following sections:

1. Creates the JavaScript namespace.
2. Registers the current physical model with the physical model that the applet uses.
3. Creates the super class.
4. Customizes a predefined presentation model to support partial refresh logic.
5. Includes the logic that Siebel Open UI runs if the user changes records.
6. Includes the logic that Siebel Open UI runs if the user changes a field value in a record.

Example of a Physical Renderer

Figure 4 describes how the partialrefreshpr.js file does a partial refresh for a physical renderer. It is recommended that you include this business logic in the physical renderer so that multiple renderers can reuse it. To get a copy of this file, see Article ID 1494998.1 on My Oracle Support. To view an example that uses this file, see Configuring Siebel Open UI to Partially Refresh Web Pages Without Calling the Siebel Server.

Figure 4. Example of a Physical Renderer

Explanation of Callouts

The partialrefreshpr.js file includes the following sections:

1. Creates the JavaScript namespace.
2. Registers the current physical renderer with the physical renderer that the applet uses.
3. Creates the super class.
4. Specifies the ShowJobTitleRelatedField property.
5. Includes the logic that Siebel Open UI runs if ShowJobTitleRelatedField changes.