My customer has an approval requirement for the Request (sc_request) level of a submitted order guide. There are 4 scenarios:
- Approval 1 and Approval 2
- Approval 1 only
- Approval 2 only
- No approval
Scenario 2-4 work as expected.
Approval 1 is a single user which is pulled from a submitted variable (it performs a lookup of an RITM to get the variable value)
Approval 2 is driven by a table where there can be multiple approval groups listed. So when the flow gets to Approval 2 it performs a lookup of that table with appropriate criteria and then performs a For Each under which it generates one approval at a time until all the approval records are accounted for.
The issues is that in Scenario 1 when Approval 1 is approved, it marks the Request approved. That triggers the flows in the RITMs to start. THEN Approval 2 is triggered and the Request Approval State is set back to 'Requested'. But of course the RITM flows have already started, so it is possible that the RITMs will start to get fulfilled even though they are not truly approved.
At this point of the flow I am not using a stage or update record action to update the Requst.
Here is the portion of the flow in question
And in the execution details you can see that step 5 Ask for Approval is returning an Approved State of 'approved'. So how does one design a flow with nested approvals without the first approval approving the record prematurely?
