Issue with 'Rollback To' in Workflow

Community Alums
Not applicable

‎06-10-2024 04:21 AM

Hi All,

I have a scenario, where I have 3 group (A, B, C) approvals under 'Approval Coordinator'. So, if any member in any of the groups reject, it should roll back and come to 'Approval Coordinator' requesting for the re-approval. 

A member from the group A rejects the approval. It is rollbacking and requesting for the approval from the same group A. Rest B, and C are getting 'No Longer Required'. Why is that? Shouldn't it make all the group members from A, B, and C as 'Requested'? Also under the 'Group Approvals' tab, why is that B, and C are showing as 'Approved' while A is showing as 'Requested'?

 

Requests.PNGGroup Approvals.PNGWorkflow.PNG

 

Regards

Suman P.

0 Helpfuls
  • 368 Views
5 REPLIES 5

Community Alums
Not applicable

‎06-10-2024 05:02 AM

Hi @OlaN,

I am in need of help. Kindly help.

Regards

Suman P.

 

0 Helpfuls

OlaN
Giga Sage
Giga Sage
In response to Community Alums

‎06-10-2024 06:10 AM

Hi,

Why should the Workflow go back to Approval coordinator if it's been rejected by the Group approval ?

Then there is no way the Group approval can reject, because it will always end up as a new approval again and again and again.
This kind of logic seems broken to me, I would advise to have the Workflow finish in a rejected state if the approval gets rejected by the group.

0 Helpfuls

Community Alums
Not applicable
In response to OlaN

‎06-10-2024 06:15 AM

Hi @OlaN,

I know this is a stupid requirement, but there is a way to get out of loop. We can add Turnstile element to limit the iterations.

0 Helpfuls

OlaN
Giga Sage
Giga Sage
In response to Community Alums

‎06-10-2024 11:10 PM

Well that's a way to stop the neverending loop, but still a workaround in my humble opinion.

To answer your question on why the other approvals is set to "No longer required"; the answer is, it depends on the rules you've setup for the approval.

You can configure the approval to reject if ALL members reject, or if ANY member reject, and a bunch of other variations in between.

In this case it seems you set it to reject if any member reject, so, in that case all the other approvals will be set to "no longer required" because of the approval rule.

The next iteration, new approval records will be created again for the same record, and all of them will be set to "requested" at start, and the status will change when the approval gets answered.

 

Hope I'm making sense here, kind of hard to explain in text.