I took my first shot at creating a Flow for a new Service Catalog item. The flow works correctly for the most part, however, we have 3 levels of approvals which need to be met in order to generate the final catalog task.
The first approval to the manager is met correctly, however, the two additional approvals below that, reset any prior approvals.
The second approval step, will update the prior manager approval back to "Requested" when it was already approved. (work notes on the manager approval log the 3 state/field changes: requested, approved, then back to requested)
The third approval step will reset the prior two approvals, as well as send email notifications to the prior requestors. (who had already approved) We do not see this behavior with the older "workflows" we have for other catalog items. Has anyone else experienced this? I've included a few screenshots of the flow, I can expand any step if needed. Thank you in advance!
I recently ran into this exact same issue with approvals in flow designer and after a deeper investigation I discovered that Approval Engines were still enabled on the Requested Item table which was causing the conflict between approvals generated in a flow versus older approval engines.
When I selected "Turn Engines Off" the issue was resolved and approval engines were no longer able to be set on the table.
