Boundary Escalation

Some processes are very time sensitive, to be able to react to tardy finished tasks, the use of Boundary Escalations is recommended. These become effecive, as soon as only a given time for a task is remaining.

Not interrupting escalation

A not interrupting escalation can identified by the dashed border in the process image. It will not interrupt the normal process sequence, but functions like a parallel gateway, which is activated, when the lodged remaining time is reached.
This is useful, if e.g. a reminder should be sent.
The example process has a not interrupting escalation, so that an hour before expiration of time for the task “Get Food Wishes” a automatic reminder mail is sent via Mailnode.

Interrupting Escalations

When an interrupting escalation is effective, the “normal” process sequence is interrupted and the Boundary Escalation path is taken.

The interrupting escalations can be identified by the solid border.

Shown with a concrete example it is as follows:

In the example process someone has to ask for the customers' special food wishes. If this task is not finsihed on time, the normal process sequence does not make any sense anymore, because not enough time is remainig to purchase special ingredients and prepare special food.

If the task “Get Food Wishes” exceeds the time by 60 minutes, the process is automatically taken to “Prepare Standard Food”.

Endings

Depening on whether a instance should be completely terminated when finishing one path or only the path one of the two endings is used.