Siebel Business Process Designer Administration Guide > For Developers: Understanding How Workflow Processes Are Designed > Handling Events >

Using Run-Time Events

Run-time events allow the Siebel application to respond in real time to user actions. Run-time events can be specified in the branches for Start, Wait, or User Interact steps to start or resume a workflow process. The fields in the WF Step Branch applet that are used to define a run-time event are described in Field Descriptions: WF Step Branch Applet and are the following:

  • Event Object Type
  • Event Object
  • Event
  • Sub Event
  • Event Cancel Flag

NOTE:  When defining run-time events within a workflow process, a run-time event should not be repeated. You cannot use the same event more than once within a workflow process.

Run-time events can be used for workflows that run within a user session. For workflows that span across multiple users—long-running workflows—use user events instead. For more information, see Using User Events.

NOTE:  Run-time events should not be used to trigger long-running workflows because a run-time event is specifically attached to a single user and a single session. A run-time event is only for that single user, as it stems from Personalization functionality. Instead use an interactive workflow or a service workflow to handle the run-time event, then after processing it and validating it, generate a user event to notify a long-running workflow.

For further information on run-time events, see Siebel Personalization Administration Guide.

Run-time Events and User Interact Steps

The following events are not supported with the User Interact step:

  • All application events.
  • The DisplayRecord event.
  • The DisplayApplet event.
  • The SetFieldValue event for a field that has the Immediate Post Changes property set to TRUE.
  • The Login event. Use the WebSessionStart event instead.

Choosing Between Using Run-Time Events and Using Workflow Policies

In cases when it is necessary to detect database events, use workflow policies, not run-time events, for defining integrations that occur on data change or write. For example, when using the UI, use run-time events to trigger a workflow process. When using the Siebel EAI Adapter, which performs numerous WriteRecord events, use workflow policies.

Siebel Business Process Designer Administration Guide