Event Subprocesses

An event subprocess executes an internal subprocess when an event is triggered. You can use event subprocesses within business processes and pageflows.

For more information, see " Event Handlers" in the TIBCO Business Studio - BPM Edition Concepts Guide.

Collapsed:

Expanded:

Note the following when using event subprocesses:

• A process can contain zero or more event subprocesses of any supported type or configuration.
• Each event subprocess must start with a single start event.
• There is no in-process communication between event subprocesses (sequence flow, signals etc).

You can use event subprocesses with the following start events:

• Event Subprocesses placed in a Business process: Message Start Event and Signal Start Event
• Event Subprocesses placed in a Pageflow : Signal Start Event and Type None Start Event

Business processes support interrupting or non-interrupting event subprocesses.

This is defined on the start event of the event subprocess by checking Interrupt Process Flow or Continue Process Flow. This affects the process as follows:

Interrupt Process Flow:

• The main process flow is suspended until completion of the event subprocess.
• This does not affect the processing and completion of individual activities that are already in progress related to the process instance. However, those activities outgoing flow is not processed until the event subprocess completes.
• This does not affect the processing of other event handler flows, event subprocesses and ad-hoc activities.
• This does not affect the processing of activities in active reusable subprocesses.
• Incoming events, submits, subprocess completions and so on in the main process are preserved but ignored until the event subprocess has completed.

Continue Process Flow :

• The main process flow is not suspended during processing of the event subprocess.
• All activity can continue as normal.