Go to primary content
Siebel CRM Configuring Siebel Open UI
Siebel Innovation Pack 2016, Rev. A
E52417-01
Home
Contents
Index
Previous
Next
View PDF
List of Figures
2-1 How Siebel Servers Use SWE Tags to Render Containers on the Siebel Server
2-2 How Siebel CRM Handles Data in Siebel Open UI
2-3 How Siebel CRM Renders Objects in Siebel Open UI
3-1 Architecture You Can Use to Customize Siebel Open UI
3-2 Class Structure of Plug-in Wrappers
3-3 Example of How Siebel Open UI Renders a View or Applet
3-4 Example of a Presentation Model
3-5 Example of a Physical Renderer
3-6 Example of a Plug-in Wrapper
3-7 Stack That Siebel Open UI Uses to Render Objects
3-8 Example Stack That Siebel Open UI Uses to Render Objects
3-9 Items in the Development Architecture You Can Modify
3-10 Comparing Server Architecture Between High Interactivity and Siebel Open UI
3-11 Comparing Client Architecture Between High Interactivity and Siebel Open UI
3-12 Life Cycle of a Physical Renderer
3-13 Example of the Life Cycle of a User Interface Element
4-1 Setting Up the Presentation Model
4-2 Customizing the Setup Logic of the Presentation Model
4-3 Customizing the Presentation Model Logic to Identify the Records to Delete
4-4 Customizing the Presentation Model to Delete Records
4-5 Customizing the Presentation Model to Handle Notifications
4-6 Attaching an Event Handler to a Presentation Model
4-7 Customizing a Method in the Presentation Model to Store the Field Values of Records
4-8 Setting Up the Physical Renderer
4-9 Customizing the Physical Renderer to Render the Carousel
4-10 Customizing the Physical Renderer to Bind Events to the Carousel
4-11 Customizing the Physical Renderer to Refresh the Recycle Bin
4-12 Creating the Plug-in Wrapper
4-13 Customizing the Plug-in Wrapper to Display the Control Identity
4-14 Customizing the Plug-In Wrapper to Bind Custom Events to a Control
4-15 Customizing the Plug-In Wrapper to Define Custom Events
4-16 Customizing the Plug-In Wrapper to React to Value Changes of a Control
4-17 Attaching the Plug-in Wrapper to a Control
5-1 Contacts List That Allows Users to Change the Applet Visualization
6-1 Hierarchy That the Base Physical Renderer Class Uses
6-2 Example of How Siebel Open UI Identifies the JavaScript Files It Must Download
6-3 Example Manifest Administration
7-1 Example of a Resource Scheduler
B-1 Flow That Saves Records If the User Uses a Shortcut
B-2 Flow That Saves Records If the User Uses the Save Menu
B-3 Flow That Siebel Open UI Uses if the User Clicks an Applet in a View
B-4 Flow That Siebel Open UI Uses if the User Navigates to a View
B-5 Flow That Handles Focus Changes in Form Applets
B-6 Flow That Handles Focus Changes in List Applets
B-7 Flow That Notifies the Siebel Server
B-8 Flow That Sends a Notification State Change
B-9 Flow That Creates New Records in List Applets, Calling the Siebel Server
B-10 Flow That Creates New Records in List Applets, Processing the Server Reply
B-11 Flow That Creates New Records in List Applets, Updating the User Interface
B-12 Flow That Creates New Records in List Applets, Updating the Proxy and Presentation Model
B-13 Flow That Handles Navigation to Another Row in List Applets
B-14 Flow That Handles the Pagination Button in List Applets
B-15 Flow That Handles a Column Sort in List Applets
B-16 Flow That Handles a Cell Click in List Applets
B-17 Flow That Handles a Cell Edit and Blur in List Applets
B-18 Flow That Handles a Drilldown in List Applets
C-1 Skeleton Structure of the Plug-in Wrapper