SBM Orchestration Guide → Orchestration User Interface → Event Definition Editor
The event definition Property Editor is displayed when you select an event definition in App Explorer. The tab displays the details of an event definition that SBM automatically creates when an application workflow is linked to an asynchronous orchestration workflow using the Action Wizard, or an event definition that you create or import using the Event Definition Configuration dialog box. (See Using the Action Wizard for information about the Action Wizard.)
Each event is defined by an object type and an event type. When an event is fired during the execution of a transition, information is passed to the asynchronous orchestration workflow. The event definition editor shows what the information could be.
|The object types defined in the event definition.
|The event types defined in the event definition.
|The data sent with the event, shown in the Extension node. You can define data elements when you create a new event definition. If you import the event definition, the Extension node includes the field data and additional data you specified when you created the event definition (see Event Editor).
You can use the event types below to prioritize events. For example, to prioritize synchronous events over asynchronous events, ensure that all asynchronous events are assigned one of the INCONTROL event types. Alternatively, to lower the priority of synchronous events below Application Engine asynchronous events, you could assign them one of the INCONTROL event types.
|INCONTROL LOW Event
|Lowest event priority.
|Recommended event type for external asynchronous events.
|INCONTROL HIGH Event
|LOW Priority Event
|Assigned to all asynchronous events by default, including those generated by Application Engine.
|MEDIUM Priority Event
|HIGH Priority Event
|Assigned to all synchronous events by default. It is not recommended to assign this event type to asynchronous events to prioritize them over synchronous events.
|CRITICAL Priority Event
|Highest event priority. Use only if you are certain that an asynchronous event should be executed prior to all other asynchronous events and synchronous events.
By default, synchronous events from Application Engine are assigned HIGH Priority Event status and asynchronous events from Application Engine are assigned LOW Priority Event status. This gives priority to orchestrations that are executed when a user performs a transition in the browser interface so that users are not waiting unnecessarily.
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.