I'm really still a novice but you could create not approval forms but regular forms with a checkbox for each and have them all be triggered immediately (branch) after the process is triggered. When everyone has submitted an answer, you can use the condition to test if all have been approved and then do whatever you want -- like send diferent emails or different forms based on whether every approved or not.
Hi Daniel,
I understand that currently Process Automation has a limitation with parallel approval tasks. I tried your approach as a work around, but then the issue is the workflow gets stuck at the step before the branch. In my case, the branching happens after an If condition and whenever the condition is true, the flow never reaches the form inside branches.
To verify I moved the task out of the branch and then the flow was able to execute the form without any issues. In your case, were you able to deliver the tasks to the inbox of your branch form recipients?
When the form was created as below, flow reached the form recipient.
Can you please suggest if I am doing something wrong over here.
Regards
Johnson
Task getting stuck when the form is inside branch
Bluesky| User | Count |
|---|---|
| 15 | |
| 9 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.