Bookshelf Home | Contents | Index | Search | PDF

Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes >

Using Runtime Events

---

Runtime events allow the Siebel application to respond in real time to user actions. Runtime events can be specified in the Start, Wait, or User Interact steps in the Next Steps applet to start or resume a workflow process. There are four columns in the Next Steps applet that are used to define a runtime event:

Event Object Type. The type of object to which the event occurs. This can be an application, business component, or applet.
Event. The specific event that happens to the object. The set of available events is different for different object types.
Event Object. The name of the application, business component, or applet to which the event occurs.
Sub Event. Used when the object type is BusComp or Applet and the event is InvokeMethod or SetFieldValue. The subevent is the name of the method or business component field to be monitored.

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

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.

Workflow policies should be used if it is necessary to detect database events. You should use workflow policies instead of events for defining integrations that occur on data change or write.

For more information on runtime events, see Personalization Administration Guide.

Bookshelf Home | Contents | Index | Search | PDF