Escalation Event

escalation boundary event

An Escalation event is similar to an Error event, except that its default behavior is non-interrupting.

escalation end event

An Escalation boundary event on a subprocess catches an Escalation trigger thrown by either an Escalation end event or throwing intermediate event in the child level. A Trisotech extension in Workflow Modeler allows the Escalation trigger to be caught also by an event in the same process level as the throwing event.

Although it is normally non-interrupting, an Escalation event may be defined as interrupting, in which case it acts like an Error event.

In Workflow Modeler, this event can specify an Escalation code and/or time expression.

When escalation code is set, this event node will wait until matching escalation is thrown (by either intermediate or end escalation event).

When time expression is set, this event node will wait until given time elapses and then trigger escalation automatically.

When both (escalation code and time expression) are set then whichever arrives earlier will trigger the escalation.

Time expression can be relative to two points in time:

  • activation - it calculates expiration time from the timestamp when the node was activated - this is the default

  • lastUpate - it calculates expiration time based on last update of the process instance and by that it might require reschedule