Flow designer sequential approvals

[Jonathan63]

I am trying to create sequential approvals using the flow designer so that I can have multiple levels of approval on a single catalogue item.

In the legacy workflow, I can create multiple approval steps without impacting the parent RITM record, and I can then set the approve or reject value based on the outcome of those actions.

With the flow designer, when the first approval is approved, the flow sets the approval field on the RITM to "Approved", then changes it back to "Requested" when the next approval in the sequence is generated. I have tried removing the "Approval field" from the action config but this hasn't made any difference. This is of course unacceptable behaviour because we will have multiple updates for approved and requested on the RITM...the RITM approval field should only update once all approvals in the sequence have been approved or rejected.

How can we achieve this behaviour with flow designer?

I have seen this forum post which about the same issue but the solutions in the replies are unfortunately not working:
https://community.servicenow.com/community?id=community_question&sys_id=00d918b1db63941011762183ca96199c

Cheers

[Daniel Draes]

How's the rest of your flow? The ask for approval step seems fine.

[s_renjarnbo]

Here is my entire flow:

2nd approval:

If 2nd approver approves:

rest of flow:

[Daniel Draes]

Does the flow actually stop on the second approval and wait for one or not?

If not it could be that the approvers are the same users in the end. Hence it doesn't ask them again. Just an assumption.

[s_renjarnbo]

The flow is working perfectly - it waits for the second approver. When 2nd approver approves the RITM is marked as approved and everything is working fine.

My only problem is about the first approver, and that the RITM for a short period is updated to state = Approved which means that my SLA kicks in... shortly thereafter the RITM state is set back to Requested......

[s_renjarnbo]

Hi Daniel

The flow works perfectly - it stops where it should and continues when it should.

Only problem is the short update of the RITM approval field which then triggers the SLA related task to be created to soon

Regards

Søren