I have an approval contains say 10 approvers from different stakeholders, if I set it to 'wait for other responses before deciding, how can I request approval again just from those who rejected the approval, and keep the approved ones as is. Hence the workflow will just wait till all the rejected one re-approve again then move on. Seems if I go back to awaiting approval again, it will wipe out all approved and rejected, asking all to do it again, which will annoys the already approved approvers.
Can you give some background information as to why people first reject and then would approve something? If the thing they approve did not change, then why are they suddenly approving? If the thing they approve did change, doesn't it make sense for the people who approved (something different, because it has now changed) to look at it again and see if they (still) approve?
Thx Willem for your reply, because the ticket contains different sections which each approver is approving for their own part, so approver A won't be concern about section B which should be only look at by approver B.
We also don't want to split up the approval process in linear way that will hold up the approval process, hence we send approval out in parallel to everyone in one shot.
For you purpose can you look at using the Approval Coordinator workflow activity? This can include multiple regular approval workflow activities like group approvals. When all approve the Approval Coordinator workflow activity approves and continues the workflow. This way you can reset just one group (f.e. approver A) and the rest will still be there. And only when the complete block matches the approval is handled.
