Overview of the Siebel Open UI Client Application Programming Interface

Creating a custom client user interface in Siebel Open UI requires that you do the following work:

• Creating a new presentation model that Siebel Open UI uses in addition to the metadata and data that it gets from the Web Engine that resides on the Siebel Server.

• Creating a new physical user interface by creating a custom physical renderer that Siebel Open UI uses in addition to a predefined or custom presentation model.

You can use the following programming interfaces to implement these presentation models:

• Presentation model class. Describes the life cycle methods that you must code for a presentation model and the control methods that Siebel Open UI uses to add presentation model properties and behavior. For more information, see "Presentation Model Class".

• Physical renderer methods. Describes the life cycle methods that you must code into any renderer that binds a presentation model to a physical renderer. For more information, see "Physical Renderer Class".

For a summary of these methods and information about how Siebel Open UI uses them, see "Life Cycle of User Interface Elements".

Siebel Open UI defines each class in a separate file. It stores these files in the following folder:

\build_number\EAPPWEB\PUBLIC\language_code\build_number\SCRIPTS\SIEBEL

For brevity, this chapter states that the method does something. In reality, most methods send a request to a proxy object, and then this proxy object does the actual work.

For more information about the language_code, see "Languages That Siebel Open UI Supports".