Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Process Modeling Concepts : End Events

End Events
An end event indicates when the process has completed. They are optional, however if a process contains a start event, it must contain an end event. End events have different types that indicate different results upon completion of the process. All end events are "throw" events:
None  There is no specific end result to the process.
Message  Indicates that a message is sent at the end of the process. The message can either be a response to the start message, or a different message. This can be implemented using a web service using the Solution Design capability (see "Implementing Message Events" in TIBCO Business Studio Modeling Guide).
Signal  Indicates that a signal is broadcast at the end of the process. A signal end event broadcasts a default signal name (signaln).
Multiple  Indicates that there is more than one result that will occur when the process ends.
Error  Ends all activities in the process immediately without compensation or events, and appears in the Event log as a failed process instance.
Compensation  Indicates that a compensation is necessary. For more information, see the BPMN specification at http://www.bpmn.org.
Cancel  Used within a transaction sub-process to trigger a cancel intermediate event attached to the sub-process boundary.
Terminate  Ends all activities in the process immediately without compensation or events.
Throw and Catch Events
An event that is located in a sequence flow can "throw" an event that can be "caught" by a catch event. Additionally, throw events are distinguished from catch events on a diagram by having their symbol colored in:
Catch intermediate events can be placed in flow, or on a task border. An in-flow catch event halts the flow until the event is triggered. A catch event attached to a task border usually cancels the task when the event is triggered.
Triggers and Results
An event trigger defines the cause for the event (for example, an error elsewhere in the Process). An end event result indicates the consequence of a sequence flow ending (for example, the sending of a message).
Triggers and results can either be "thrown" by events, or "caught" by other events as described.
Palette Summary
The following table summarizes the BPMN events that are available to you on the palette in TIBCO Business Studio:
catch  throw
Event Handlers
Event Handlers are supported in Business processes and Pageflow processes. You can use event handlers to execute a flow that is separate from the main flow of the process (for instance to update process data used by the main flow).
Event handlers can be triggered zero or more times during the life of a process instance.
While an event handler allows you to do something multiple times during a process, it does not have to happen for the process to complete.
An event handler is a catch intermediate event with no incoming flow. Event handlers with no specific trigger type will normally be triggered through a destination-specific API or utility. See the BPM Developer's Guide for more information.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved