Explicitly tracking the overall status of a process

[herrier]

Hi, is modelling the status of a process explicitly through the use of an intermediate event with an execution listener an acceptable pattern?

In the example below, I set a process variable to “In Review”, “In Approval” and “Approved” using an execution listener on the intermediate events (and the end event). This is very explicit and clear in my opinion but I rarely see this is any example on the forum (or elsewhere). I know the same effect can be achieved with a task/execution listener on the user tasks but the status changes are less obvious then.

I don’t think a “blank” intermediate event like this translates to Camunda 8 either?

Thank you!

[hassang]

Hi @herrier

They are especially useful for monitoring to understand how the process is doing, for example, as milestones or key performance indicators (KPIs)

https://docs.camunda.io/docs/components/modeler/bpmn/none-events/#intermediate-none-events-throwing

https://docs.camunda.io/docs/components/best-practices/modeling/modeling-with-situation-patterns/#option-1-showing-milestones

[herrier]

Hi @hassang - thanks for those links to handling this in v8 and also the best practice docs. It makes complete sense to explicitly model this not just for readability of the process but as you say for metrics, wait times in states etc.