Approvals are going to No longer required State

Siddhesh Gawade
Mega Sage
Mega Sage

Hello,

 

I am creating a flow, were I wanted to regenrate approvals based of some conditions. The approvals are gettings created correctly. But, when I reject the approval, and when the conditions mets I wanted to create approvals again. They are getting created but going into "No longer required" state. 

 

see the activities from record on which I wanted to create the approvals:

SiddheshGawade_0-1722190721838.png

 

after rejected state, once the approvals are created again, the 'approval' field is changing to requested but the system updating it to 'No longer Required'. 

 

Just for testing, I tried creating approvals again, once previous approvals are accepted and it worked. System not Updating it to "No longer Required'. So the question is can what is going on when the previous approval is rejected?

Or I am miising something else or I am doing it all wrong?

See the Flow Logis:

SiddheshGawade_1-1722191040714.png

 

Please let me know, if you have any thoughts. Any help is appreciated!!!

 

Regards,

 

Siddhesh

 

1 ACCEPTED SOLUTION

Siddhesh Gawade
Mega Sage
Mega Sage

 

Hello, I found the issue!

 

As I suspected, it’s due to rejected approvals in previous steps. Once we reject the approvals, the record on which the approvals were created gets deactivated (active = false). This triggers the out-of-the-box (OOTB) functionality to update new approvals to the "No longer required" state.

 

There is an OOTB business rule called "Moot Approvals Upon Cancellation" that triggers when a record becomes "active=false" and updates the approval state to "No longer required."

 

In summary, it's the OOTB functionality causing this behavior🙂

 

Regards,

Siddhesh

View solution in original post

3 REPLIES 3

Tony Chatfield1
Kilo Patron

Hi, I think that this SNC article contains the details you need to configure this correctly.

Flow Designer Approvals Overview - Workflow Automa... - ServiceNow Community

Siddhesh Gawade
Mega Sage
Mega Sage

 

Hello, I found the issue!

 

As I suspected, it’s due to rejected approvals in previous steps. Once we reject the approvals, the record on which the approvals were created gets deactivated (active = false). This triggers the out-of-the-box (OOTB) functionality to update new approvals to the "No longer required" state.

 

There is an OOTB business rule called "Moot Approvals Upon Cancellation" that triggers when a record becomes "active=false" and updates the approval state to "No longer required."

 

In summary, it's the OOTB functionality causing this behavior🙂

 

Regards,

Siddhesh

Had the same issue, de-activating OOTB BR "Moot Approvals Upon Cancellation" resolved it for me, I confirm it's working, thanks!