The humble escalation event has arrived to the Camunda process engine.
Well actually there are technically 6 of them and while each is special in its own little way I’m going to give some examples of the most widely used ones.
Escalation events act a lot like error events with one very important difference –
You can throw an escalation event without interrupting the process instance.
A good example of the usefulness of this event can be seen in the following model:
This model describes a situation where someone needs to be made aware of an issue within the process. Specifically where processing is going to take too long, but we also don’t want the process to stop.
By using the escalation throw event the item Procurement activity can continue while the non-interrupting escalation event catches the thrown escalation and passes it on for a parent pool to deal with. In this case someone needs to be informed of a late arrival of goods.
There’s of course a lot of other ways to utilize escalation events.
In the model below i’m using a non-interrupting start event within an event subprocess.
This means that an escalation can be raised any time within the process and then caught and dealt with by the event subprocess without halting the main process itself. For more information on this shiny new addition head on over
to our documentation page.
So go forth and escalate things with Camunda 7.4!
