Option to Delete ALL Flow Approval Tasks if a Flow Instance is Terminated or Canceled

[dadams]

I think an option to delete all associated approval tasks if the flow is canceled or terminated is needed.  Maybe this setting would make sense as a paramater for the entire flow or as a paramater within the Assign a Task action. 

Currently the tasks appear to be left orphaned and assigned to the user to approve or reject even if the flow has ended and the approval is no longer need.  By having this option we can remove the clutter of orphaned approval tasks sitting in user's queues and remove the confusion of the unneeded tasks.

[fklatecki]

100% agree, admin should be able to cancel any or all pending approvals.

[ZachS15]

For any developers looking to clear an account's approvals I developed this custom script that worked for me. It just approves each card programatically using jQuery clicks. Good for a quick fix. I had over 200+ approvals pending. It can be run when in Flow on the approvals page.

//Get all approval cards on the page
var appCards = jQuery('.approval-card .actions > button:first-child');
var i = 0;

(function approveCard() {
    //Pause for each approval
    setTimeout(function () {
        //Approve the card
        appCards.eq(i).click();

        //Wait for panel to open
        setTimeout(function () {
			//Confirm approval
            jQuery('.confirmSection .fl-NgReactDefaultButton > button').click();
        }, 2000);

        //Go to next approval card
        i++;

        //If there are more cards, approve the next one
		if(i < appCards.length)
            approveCard();

    }, 2000)
})();

[K_Samad]

YES! We had to cancel and resubmit a number of Approval flows, this causes a bunch of clutter on the approver Dashboard, and when you are dealing with short attention span C-level management you only want them to see the ACTIVE requests - not the debris from cancelled submissions.

---

@dadams wrote:

I think an option to delete all associated approval tasks if the flow is canceled or terminated is needed.  Maybe this setting would make sense as a paramater for the entire flow or as a paramater within the Assign a Task action. 

Currently the tasks appear to be left orphaned and assigned to the user to approve or reject even if the flow has ended and the approval is no longer need.  By having this option we can remove the clutter of orphaned approval tasks sitting in user's queues and remove the confusion of the unneeded tasks.

---

[Luka84]

So this has been suggested a while back and probably does not have sufficient visibility to other users to vote up. It is definitely a clear necessity and should be implemented as soon as possible. Any idea if anything has been done or workarounds have been developed? thanks for the suggestion