Manual group approval not setting others to No Longer Required

[vgayathric9]

When a group approval is added manually, having one group member approve the request does not automatically change the status of the remaining approvers to 'No Longer Required'.

Is this the expected Out-of-the-Box (OOTB) behavior?

My goal is to find a way—even for manually created group approvals—to choose whether only one member needs to approve or if all members must approve. How can i achieve this?

@Dr Atul G- LNG @Amit Gujarathi @Ankur Bawiskar @sandeepdutt @kaushal_snow @Vikram Reddy 

[Tanushree Maiti]

Hi 

If you are using Flow, you can control following setting in flow.

1. For 'One Member Approves': Configure the approval action or activity setting to "Anyone approves". Once the first person approves, the engine automatically skips the others, setting their status to 'No Longer Required'.
2. For 'All Members Must Approve': Set the requirement to "All user approve". The workflow pauses and prevents completion until every single group member makes a decision

[vgayathric9]

Thanks for the reply Tanushree,

But these approvals are not triggered by a flow or workflow. Instead, we are adding them manually via the RITM Related List using the Edit button. When manual approvals are added this way, the system needs to provide an option to configure the approval logic—specifically, whether it requires Only One Approver from the group or All Approvers to approve.

Can you please help me on how i can achieve this?

[drbob]

Even if you _had_ set the approval up with a workflow (and presumable the same applies to a flow but I haven't tried that) manually adjusting the list doesn't update the records correctly - the approval activity in the WF waits for the original approvers. ...at least that is my previous experience - if anyone knows that this has changed then please advise.

I would suggest that you use the OOTB approval activities and put a script in there to adjust the approvers (if it's a complex but describable situation). If you really need to manually change them after they are settled then you somehow need to get the activity to re-evaluate itself (I'm not sure how easy that would be) or, as someone else said, handle it all yourself - if you start of OOTB then you typically have to carry on OOTB.

Go back to the start - why are you manually adding approvers ? If that can be avoided or replaced by some logic then you will save some effort.

[Dr Atul G- LNG]

This is expected behaviour. You need to add the logic, after which you can cancel or move the request forward. The remaining approval is no longer required.