Approval State changed to "No Longer Required" when I have 2 Ask for Approval actions

Jean-Vincent Mi
Tera Contributor

Hello community!

My first question! And concerning Ask for Approval action in the Flow designer.

I have this functional requirement : For a specific request, I need to proceed to 2 different ask for approval, and for each ask for approval action, it is a different person to approve or reject.

I created one Flow for each ask for approval, the trigger flow is configure to trigger when a sub-status is changed (I have 2 sub-status in my request, so one flow for one sub-status), the 2 sub-status are changed in same time in my case.

But, I encountered a problem and I don't know why I have this problem: when the first person approve the first approval, the second approval of my second ask for approval change to "No Longer Required" instead of just stay to "Requested" until the approve of second person.

Do you have any idea about this issue?

Thank you, Jean-Vincent.

1 ACCEPTED SOLUTION

Mahendra RC
Mega Sage

Hello Jean,

I believe you can implement your requirement using a single flow it will be easier to manage and also easier to debug the issue in future. You can run the actions in parallel and implement the flow as per below logic (just a sample):

1. If 1st sub-status != to_validate_by_cr --- If you flow retrigger because of the change only in 1st sub-status field than the approval will be re-triggered for 1st Sub-status and not for 2nd sub-status
--> Wait for 1st Sub-status to change to to_validate_by_cr
--> Ask for Approval
--> if CDG Receiver approved
--> Update 1st Sub-status to Validated by CR
Continue with your flow steps
2. If 2nd sub-status != to_validate_by_cf  --- If you flow retrigger because of the change only in 2nd sub-status field than the approval will be re-triggered for 2nd Sub-status and not for 1st sub-status
--> Wait for 2nd Sub-status to change to to_validate_by_cf
--> Ask for Approval
--> if CF Receiver approved
--> Update 1st Sub-status to Validated by CF
Continue with your flow steps

Please mark this as helpful/correct, if this answer your question

Thanks

View solution in original post

8 REPLIES 8

Mahendra RC
Mega Sage

Hello Jean,

I believe you can implement your requirement using a single flow it will be easier to manage and also easier to debug the issue in future. You can run the actions in parallel and implement the flow as per below logic (just a sample):

1. If 1st sub-status != to_validate_by_cr --- If you flow retrigger because of the change only in 1st sub-status field than the approval will be re-triggered for 1st Sub-status and not for 2nd sub-status
--> Wait for 1st Sub-status to change to to_validate_by_cr
--> Ask for Approval
--> if CDG Receiver approved
--> Update 1st Sub-status to Validated by CR
Continue with your flow steps
2. If 2nd sub-status != to_validate_by_cf  --- If you flow retrigger because of the change only in 2nd sub-status field than the approval will be re-triggered for 2nd Sub-status and not for 1st sub-status
--> Wait for 2nd Sub-status to change to to_validate_by_cf
--> Ask for Approval
--> if CF Receiver approved
--> Update 1st Sub-status to Validated by CF
Continue with your flow steps

Please mark this as helpful/correct, if this answer your question

Thanks

Hi,

Thanks for your answer, I will adapt my both flows to have a unique flow. But it will be be little more complex for the second status, the specificity of this sub-status is return to previous value due to a review, and necessary to proceed to a new ask for approval again, without touch to the 1st sub-status approval. I will try with a loop and wait change.

But it seems Flow Designer do not manage Ask for Approval for a same record when it is requested by two or more differents flow executed in same time... I don't know if it's an issue from ServiceNow or the expected work.

Thank you for your help, for me, this answer to the question.

yes, but may be in a single flow if we want to get approval using approval action 2 times then it should work fine. Let's give a try to see.

Olá, estou com um problema muito parecido, vc conseguiu resolver?

no meu caso a primeira aprovação muda o estrato e deveria gerar uma segunda solicitação de aprovação, mas essa segunda solicitação gera um no longer required