|Bookshelf Home | Contents | Index | PDF|
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:
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.
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|