Siebel CRM Configuring Siebel Open UI Siebel Innovation Pack 2015 E52417-01 |
|
Previous |
Next |
View PDF |
This topic includes flowcharts that you can use to determine the methods that Siebel Open UI uses during various steps in the life cycle of a user interface element. It includes the following information:
This topic describes the life cycle flows that Siebel Open UI uses to save records.
Figure B-1 illustrates the life cycle flow that Siebel Open UI uses to save a record if the user simultaneously presses the CTRL and S keys. The numbers in the diagram indicate the sequence that Siebel Open UI uses during this flow. The A connector connects to the flow described in "Flow That Saves Records If the User Uses the Save Menu".
Figure B-2 illustrates the life cycle flow that Siebel Open UI uses to save a record if the user clicks Menu, and then the Save Record menu item. The A connector connects to the flow described in "Flow That Saves Records If the User Uses a Shortcut".
This topic describes the life cycle flows that Siebel Open UI uses when the user navigates through various items in the client.
Figure B-3 illustrates the life cycle flow that Siebel Open UI uses if the user clicks an applet in a view.
Figure B-4 illustrates the that Siebel Open UI uses if the user navigates to a view.
Figure B-5 illustrates the life cycle flow that Siebel Open UI if the focus changes for a field in a form applet. For example, if the user tabs out a field, clicks outside the field, minimizes the window, saves the record, and so on.
Figure B-6 illustrates the life cycle flow that Siebel Open UI if the focus changes for a field in a list applet. For example, if the user tabs out a field, clicks outside the field, minimizes the window, saves the record, and so on.
This topic describes the life cycle flows that Siebel Open UI uses to send notifications.
Figure B-7 illustrates the life cycle flow that Siebel Open UI uses to notify the Siebel Server.
Figure B-8 illustrates the life cycle flow that Siebel Open UI uses to send a notification state change. For more information about the notifications that this flow describes, see "Notifications That Siebel Open UI Supports".
This topic describes the life cycle flows that Siebel Open UI uses to create a new record in a list applet.
Figure B-9 illustrates the life cycle flow that Siebel Open UI uses during the call that it makes to the Siebel Server when it creates a new record in a list applet. Siebel Open UI typically calls the following methods during this flow: NewRecord, DeleteRecord, EditField, WriteRecord, and so on. For more information, see "DeleteRecord Method", "WriteRecord Method", and "NewRecord Method".
Figure B-10 illustrates the life cycle flow that Siebel Open UI uses when it processes the reply that it gets from the Siebel Server when it creates a new record in a list applet. This figure illustrates the flow that occurs after Siebel Open UI receives the reply.
Figure B-11 illustrates the life cycle flow that Siebel Open UI uses to update the user interface. The numbers in the diagram indicate the sequence that Siebel Open UI uses during this flow.
Figure B-12 illustrates the life cycle flow that Siebel Open UI uses to update the proxy and presentation model.
This topic describes the life cycle flows that Siebel Open UI uses depending on an action that the user does in a list applet.
Figure B-13 illustrates the flow that Siebel Open UI uses if the user navigates to another row in a list applet.
Figure B-14 illustrates the flow that Siebel Open UI uses if the user clicks the pagination button in a list applet.
Figure B-15 illustrates the flow that Siebel Open UI uses if the user sorts a column in a list applet.
Figure B-16 illustrates the flow that Siebel Open UI uses if the user clicks a cell in a list applet.
Figure B-17 illustrates the flow that Siebel Open UI uses if the user edits a cell in a list applet, and then navigates away from this cell.
Figure B-18 illustrates the flow that Siebel Open UI uses if the user clicks a drilldown field in a list applet.