Resetting and Re-triggering Approvals for Catalog Tasks After Rejection

[monica190]

I have a scenario where, for a catalog task, I need to generate approvals based on state change. There can be multiple groups involved, and a user from each group must approve the task for it to be marked as approved.

If any group rejects the task:

1. I need to record the rejection reason in the task.
2. Re-trigger approvals for all groups.

The task should remain in a "requested" state until all approvals are completed.

The issue I’m facing is that when a task is rejected, I remove the association of task ,group approvals and approvers, reset the task to the "requested" state, and re-trigger approvals. However, even after these steps, when I approve the task, the state says rejected. Also, the group approval shows "No longer required," even though the approvers show "Approved."

I want to ensure that approvals are fully reset after rejection so the process can restart correctly.

[Mark Manders]

How are you doing this? Flow designer or workflow? And can you share how you have set this up, that would really help.

Next to that: it sounds like a very strange process. If you reject, I am just going to ask you again and again and again, until someone finally approves. Shouldn't the rejection simply cancel the entire ticket (reject = I don't approve and just asking again won't change that).