Intermediate Events
Intermediate events include the following functionalities:
- Intermediate events can be used "in-flow" that is, between two other activities.
- Most catch type intermediate events can be attached to task boundary to catch a triggered event only whilst that task is in-progress.
- You can define an event handler by starting a flow with an intermediate event. See Event Handlers (trigger type support is destination-specific).
You can use the following types of Intermediate events:
Note: BPMN imposes some restrictions on the placement of intermediate events. Example:
- Intermediate events with theNone and Link types cannot be placed on the boundary of a task.
- Intermediate events with the Cancel type cannot be placed in sequence flow.
TIBCO Business Studio - BPM Edition allows you to place any type of intermediate event on the boundary of a task or in sequence flow; however, any invalid constructions are reported in the Problems view.
- None - Indicates an unspecified change in the process.
- Timer - The event is triggered at a specific date/time or at a regular interval (time cycle). When placed on the boundary of a task, a timer event defines a deadline for the task. In the Properties view for the event, the Use as activity deadline option is preselected. If more than one timer event is attached to a task, only one of the timer events can be selected as the timer deadline. If there is a canceling timer then it must be selected as the deadline.
There are two options you can select to decide how the task is treated if the event times out (Withdraw Task on Timeout and Continue Task on Timeout).
The timer deadline uses the appropriate system calendar to calculate when the deadline expires.
- Throw/Catch Link - Indicates a connection from one or more throw link intermediate events to a catch link intermediate event in the same parent process. This can be thought of as a "go to" or "off page connector" that you can use to break up a process for better legibility.
- Throw/Catch Signal - Broadcasts or catches a signal. A throw signal event is assigned a default signal name (signaln).
- Catch Error - Attached to a task boundary to end a sub-process with an error. The task either catches the specified error, or catches any error if no specific error is specified.
- Throw/Catch Compensation - Used to process compensating activities for previously executed tasks:
- If located in sequence flow of the process, this event throws a call for compensation.
- If attached to the boundary of an activity, this event catches a named compensation call.
- Catch Sub-Process Cancel - Used on the task boundary of a transaction sub-process. It is triggered if a cancel end event is reached within the transaction sub-process or if a transaction protocol “cancel” message is received while the transaction is being performed. It can be used as sub-process cancellation event handler.