What is the impact of turning off "approval engines" for Requested Items ?

[s_renjarnbo]

Hi

As many others my company have a lot of workflows related to - mostly - approvals of requested items.

I am trying to move to flow designer but I am having a few issues with setting up sequential approvals without updating the requested item.

Here is what happens:

1. First approval is triggered
2. First approver approves

3. Requested item state changes - briefly - to approved

4. SLA record is generated because of 3 above

5. Second approval is triggered

6. Requested item state changes back to requested

7. SLA is paused

I dont want the SLA record to be generated until ALL approvals have been collected.

It has been suggested to turn off the "approval engine" for requested items but I have no idea about the consequence of that when we have both workflows and flows for a long period.

Can anyone help me

[Brian Lancaster]

Based on docs flow designer ask for approval action replaced classic approval rules. I'm not 100% sure but I think if you turn off the approval engine it could cause problems for the workflows. I would suggest turning off approval engine for request_item in dev and test the workflows that have an approval.

[Lisa Holenstein]

Hi Sören,

there's another workaround that you can use. When you add the "Ask for approval" action, there's a field that is auto-populated: "Approval field". You can empty that, which leads to the field not being set on your requested item. Follow with an if logic to proceed if the approval record (sys_approval_approver) state is approved for your second approval and you should be fine.

Hope this helps!

Lisa

Please mark the post as correct if this answered your question.

---

Have questions about Flow Designer, PAD, or Decision Builder? Check out the Workflow Automation CoE.
Have questions about the Now Platform? Join our bi-weekly Platform Academy.

[s_renjarnbo]

Hi Lisa

Thanks for replying but unfortunately I have tried to empty that field but it still updates the RITM record as described.

I have even tried creating a custom field on the form and add that field as the approval field.

Still the same

Regards

Søren

[Vishwaveer Sing]

Hi @s_renjarnbo,
In the "Ask for Approval" action, you will have a something called as "Approval Field", change that to "Approval set" instead of "Approval" and Journal Field as "Approval history", make sure that you do it for all the "Ask For Approval" actions, this should resolve the issue.