How to design a branching task model with the final decision

We have a special process with the goal of collecting approval comments from all departments. Only one person from each department is needed to complete the approval, but the special case is that only the initiating department can end the process. Approvals from departments other than the initiating department are optional and not required. Whenever the initiating department wants to terminate or end the process in advance, they can end the process at any time. I tried many modeling methods, but ultimately failed to achieve this goal,Even if the initiating department ends the task, other departments still handle the approval process, and the entire process has not been ultimately completed. This is my model:
multi-department-parallel.bpmn (8.4 KB)

Hi BigNight, what does exactly mean “Approvals from departments other than the initiating department are optional and not required” ?
If the FinanceAudit doesn’t approve, in the sense they explicitly say “no”, can the initiating department approve anyway since it has the “final” decision?
If this is the case, then I would say that the other departments are not real approvals that influence the flow but just information that has to be provided to the initiating department that will take the decision based on that.
Does the following version fit your need?

2 Likes

Your understanding of the problem I raised is particularly precise. Thank you for providing the solution that gave me the idea to solve the problem.At the same time, it made me more fond of camunda, and the reply speed of this community is unimaginable.

1 Like