The following figure illustrates the life cycle flow that Siebel Open UI follows to notify the Siebel Server. The steps in the flow are as follows:

  1. Process the reply.

  2. Process the generic notification.

    • Run NotifyCanInvokeMethod on Presentation Model (PM) – see step 3.

    • Run NotifyCanUpdateMethod on PM – see step 4.

    • Run GetQuickPickInfo PM – see step 5.

  3. Run NotifyCanInvokeMethod on PM.

    • Run InvokeStateChange on PM.

    • Run AttachPMBinding ("InvokeStateChange") on PM.

    • Run UpdateUIButtons on Physical Renderer (PR).

    • Run ExecuteMethod ("CanInvokeMethod", methodName) on PM.

  4. Run NotifyCanUpdateMethod on PM.

    • Run UpdateStateChange on PM.

    • Run AttachPMBinding ("UpdateStateChange") on PM.

    • Run UpdateUIControls on PR.

    • Run Get("GetControls") on PM.

  5. Run GetQuickPickInfo PM.

    • Run UpdateQuickPickInfo on PM.

    • Run AttachPMBinding ("UpdateQuickPickInfo") on PM.

    • Run UpdatePick on PR.

Flow That Notifies the Siebel Server: This image is described in the surrounding text.