Approval re-assignment in Flow Designer

[SanjenFibers]

I have a flow which includes an approval action.   The approval record is subsequently re-assigned to a different approver and set to 'approved'.  The flow is then stalled - still waiting for the approval.  All works as intended if the approval is not re-assigned.

Any ideas?

[Saurabh Gupta]

Hi,
This will work if approval field on the the related task on which approval is triggered set to "approved".

Test it doing this change manually then write a BR on approval table for the same.

[jcmings]

I would explore creating a different Request Status ('state') and only push the case to 'Approved' when the correct status is met. To do this, you will likely need to create a new UI Action and display that on your form (and hide the current UI Action that "approves" the case, until the request status is correct). 

For example:

• Form #001 is submitted and routed to Group A for approval. The case is in "Awaiting First Approval" state and the Approval is "Requested." Group A clicks "Approve Case" and the state changes to "Awaiting Second Approval." 
• Form #001 is now routed to Group B for approval. Because it is in "Awaiting Second Approval" state, the UI Action to "Close" the case appears. When this "Close" button is clicked, the case status (state) changes to "Approved" and the Approval changes to "Approved."

You could also modify the flow directly to change how the routing works! There are a bunch of different OOTB "Approval" choices that you can utilize.

[SanjenFibers]

After a discussion via HIWAVE, it has been determined that managing approvals in this way is not supported by Flow Designer.  It was recommended we call workflow from Flow Designer.  Not sure what is going on, but we appear to be unable to move forward in our attempts migrate from workflow to Flow Designer for processing service catalog requests as the tool does not give us the same essential flexibility as our existing workflow-centric implementation.