End events, signals and form events

This page describes the events you can add to a workflow, other than the Start Event.

End Event

An End Event ends the process. To add one, drag End Event from the palette, or click Append finish event on the last element of a path. Its only settings are the ID and the Name (default: “Finish”).

To change the kind of end event, click Change type on it:

End event	What happens when the process reaches it
Regular end event	The process finishes successfully. Elements that are still running on other paths are stopped.
Failed end event	The process ends with the status Failed.
Cancel end event	The process is canceled. Elements that are still running, such as open forms, are canceled too.

In a Sub Process, a regular end event ends the sub process, and the main process continues after it.

Signal (Wait)

Signals let one part of a process, or another process, tell a waiting process to continue.

• A catching signal waits until a signal with its name is sent, and then the process continues. Drag Signal (Wait) from the palette to add one.
• A throwing signal sends a signal and continues right away. To make one, add a Signal (Wait), click Change type and select the throwing signal.

Setting	What to enter
Name	The name shown on the canvas (default: “Signal”).
Signal Name	The name of the signal. A catching signal continues when a signal with the same name is sent.
Scope	Throwing signals only. Which waiting signals receive it. See below.

Scope	Who receives the signal
BPMN SubProcess	Catching signals in the same sub process. Shown only inside a sub process.
BPMN Process	Catching signals in the same process.
Business Process	Catching signals in all the running processes of the same business process.
Project	Catching signals in all the running processes of the project. Also starts a new process of every workflow in the project that has a signal start event with this name.

Select the Scope of every throwing signal, even if you want the first option.

Form events

Form events start a separate path from a Form / Session while the form is still open. To add one, click the form, and then click:

• Append form created event: the path starts as soon as the transaction is created. Use it to send an invitation message to the recipient.
• Append form expired event: the path starts when the form expires before it is submitted. Use it, for example, to notify an agent.

The event is attached to the edge of the form on the canvas, and is named “Created” or “Expired”. The form created event has only an ID and a Name; the form expired event has no settings. Connect the elements of the path after the event.

Elements after a form event can use the form’s session output, but not its result, because the form is not submitted yet.