Allow you to delete (not just archive) old Workflows
I have created some test workflows, but I can only test them by activating them and now am unable to 'clean up' the workflow list before rolling out to team.
I don't have an opinion on archiving, but could see why some people would like to keep it. Deleting a draft would be helpful (again, I'm more concerned w/ deleting previously active workflows) and it makes sense that a workflow should be de-activated first in order to delete it, & it might mitigate accidental deletions.
1- Archive could have it's place. It is like "inactive." Say if you had a workflow that only ran a certain time of year and wanted to remove it as an option for the other part of the year. I think archive and delete should be two different things.
2- The ability to delete any type of workflow would be great.
3- Yes, that would provide extra protection so an active workflow wasn't deleted in haste.
Hi everyone! I just have a few more questions on this one after talking with my team today.
1) Do you have any use for the ARCHIVE feature, or would you just prefer that Archive be DELETE instead?
2) Would you want to be able to delete DRAFT workflows?
3) If we keep Archive, are you okay with only having the ability to delete Archived or Deactivated workflows? (IE: You wouldn't be able to delete Active workflows- they would need to be deactivated first)
We just want to make sure we implement this in the right way so that it meets all of your needs, so please let us know what you think about the above questions! Thanks everyone!!
I just realized that it isn't possible to delete deactivated workflows. Another excellent option would be to edit deactivated workflows so that they can be used. Make them more dynamic.
@Kylee Long Being able to delete workflows would make for a cleaner list over time, assuming we use it for years. Right now I have two "TEST General Discovery" workflows and some other "TEST" workflows that are deactivated and/or archived. I could rename them to distinguish them, but if I can't reactivate/de-archive them, what's the point of keeping them if they didn't work etc.
Hi! I just wanted to make sure I understand exactly what is needed here. Is there a reason that Delete would work better for you than the Archive option? Is it simply that you want a way to permanently clean up workflows and not just "hide" them? This has been on our "to do" list for a while, but we want to make sure we approach it knowing exactly what you need. Thanks!
Hi everyone! We just released this feature yesterday! Please let us know what you think once you try it out. :) Have a great day!
Like @Shannon Moats suggestions.
I don't have an opinion on archiving, but could see why some people would like to keep it. Deleting a draft would be helpful (again, I'm more concerned w/ deleting previously active workflows) and it makes sense that a workflow should be de-activated first in order to delete it, & it might mitigate accidental deletions.
1) Yes, we may no longer use certain workflows but I would want to keep it for historical reference.
2) Yes. When I'm working on a workflow or exploring the process, I may simply want to start from scratch. Just delete it and start a new one.
3) Yes, having a workflow deactived or archived would be a logical requirement to access the delete function.
1- Archive could have it's place. It is like "inactive." Say if you had a workflow that only ran a certain time of year and wanted to remove it as an option for the other part of the year. I think archive and delete should be two different things.
2- The ability to delete any type of workflow would be great.
3- Yes, that would provide extra protection so an active workflow wasn't deleted in haste.
Hi everyone! I just have a few more questions on this one after talking with my team today.
1) Do you have any use for the ARCHIVE feature, or would you just prefer that Archive be DELETE instead?
2) Would you want to be able to delete DRAFT workflows?
3) If we keep Archive, are you okay with only having the ability to delete Archived or Deactivated workflows? (IE: You wouldn't be able to delete Active workflows- they would need to be deactivated first)
We just want to make sure we implement this in the right way so that it meets all of your needs, so please let us know what you think about the above questions! Thanks everyone!!
I just realized that it isn't possible to delete deactivated workflows. Another excellent option would be to edit deactivated workflows so that they can be used. Make them more dynamic.
@Kylee Long Being able to delete workflows would make for a cleaner list over time, assuming we use it for years. Right now I have two "TEST General Discovery" workflows and some other "TEST" workflows that are deactivated and/or archived. I could rename them to distinguish them, but if I can't reactivate/de-archive them, what's the point of keeping them if they didn't work etc.
Hi! I just wanted to make sure I understand exactly what is needed here. Is there a reason that Delete would work better for you than the Archive option? Is it simply that you want a way to permanently clean up workflows and not just "hide" them? This has been on our "to do" list for a while, but we want to make sure we approach it knowing exactly what you need. Thanks!
Yes! I too made tests and now cannot get rid of them. Also when I deactivated one I cannot do anything with it.
Please allow this! I have a test workflow under a name that we will want for an actual workflow. I just want it deleted now.