Arbor Workflows: How to Delete a Workflow

Delete a workflow from the Workflows index by selecting the three-dot menu and choosing Delete. Deletion is permanent and hides its history from Workflow Runs. To preserve historical data, hide the trigger, disable school rollouts, or move the workflow to an archived collection.

 

How to Delete a Workflow 

Whether you are finishing a temporary process, replacing an old procedure or just want to clean up your 'playing around' workflows, you can easily remove a workflow.

To completely remove a workflow from active use, follow these steps within the Workflows index:

If you using your full screen size, as you hover over the row of the workflow you want to delete, three dots will appears at the very end of the row on the right hand side.  If you are not using full screen you will have to use your browser scrolled to access the end of the row. The dots will only appear once hovering over the row.

Select these three dots and Delete will be present in the dropdown.

Deleting a workflow is permanent and cannot be undone - so triple check you are in the correct workflow before deleting.

 

What Happens to My Workflow Data?

A common question is whether deleting a workflow wipes out historical data and logs.

  • Immediate Effect: The workflow and its history are instantly hidden from your Workflow Runs page to keep your workspace tidy. You and your team will no longer see past runs of this workflow in your active logs.

Sometimes you may want to keep the associated data with the workflow so deleting it may not be the best alternative. There are a range of alternatives to deleting the workflow and we will explore these below.

 

Alternatives to Deletion: 

If you want to stop a workflow from running but do not want to lose visibility of its past data on your Workflow Runs, do not delete it. Instead, use these native features built into Review & Test and structural settings:

 

Make the Workflow Trigger Invisible

Instead of deleting, head to Review & Test on the workflow and toggle the visibility setting off for 'Show the start form on Workflow forms when live'. This takes away the  visibility for everyone on the 'Workflow Forms' page and stops the ability for new trigger forms from being accessed. 

As this doesn't delete the workflow all historical run data stays available on your workflow Runs. If a user has the trigger url stored locally, they will still be able to access the trigger form but not complete or submit it.

 

 

Toggle Off School Rollouts

If you are managing workflows from a central MAT team, you don't need to delete a workflow to pull it back. Go to the Review & Test area and toggle off the specific schools that no longer require it. 

Turn this toggle to off to ensure schools can no longer access this workflow. 

 

This cleanly removes it from their local dashboards. If a user has the trigger url stored locally, they will still be able to access the trigger form but not complete or submit it.

 

Move it to an "Archived" Workflow Collection 

If your tier supports Workflow Categories (formerly known as Habits and Collections), you can create a dedicated folder named something that is easy for you to identify - "Out of Use" or "Archived Workflows". This should be done in combination with one of the above to ensure the workflow is not continued to be used. Grouping inactive workflows here keeps your primary dashboard clean while leaving your historical data perfectly intact and searchable.

 

 

 

Was this article helpful?
0 out of 0 found this helpful
I'm still stuck!

Comments

0 comments

Article is closed for comments.