It’s quite common for a workflow to launch multiple identical activities and have to wait for them all to complete before continuing. For example, cash is generated from a portfolio and a process needs to be started for each client in the portfolio to be paid their share. Once each client has been processed, the central admin for the payout can be wrapped up.
How is such a scenario typically modelled and handled in the Camunda world?
Hi @Ettery,
In BPMN, you can mark an activity as multi-instance, meaning that it is executed multiple times either based on static configuration or based on a dynamic condition or collection variable. See https://camunda.org/bpmn/reference/#activities-task (scroll to Multiple Instance) for an introduction on this and https://docs.camunda.org/manual/7.7/reference/bpmn20/tasks/task-markers/#multiple-instance for the Camunda implementation reference. In Camunda modeler, the multi-instance marker can be toggled via the context menu of an activity.
Cheers,
Thorben