The problem is that when the task is completed the decision is written to the global process variable approvalTask_result. The second person who completes the task sees the result of the first person. Even if the second person says "No", the "yes" condition will be true, because the approvalTask_result stores the decision of the first person.
The approvalTask_result should be saved to the scope of the subprocess.
There is a process with a parallel sub-process:
The model json: task-subprocess-test.zip
For "Yes" and "No" sequence flows the following conditions are automatically generated:
The problem is that when the task is completed the decision is written to the global process variable
approvalTask_result
. The second person who completes the task sees the result of the first person. Even if the second person says "No", the "yes" condition will be true, because theapprovalTask_result
stores the decision of the first person.The approvalTask_result should be saved to the scope of the subprocess.