Hi All,
I have seen a number of suggestions about adding a Disable Workflow checkbox to the back end workflows but could not find any in the Ideas Board, so have added on.
https://bubble.io/ideaboard/mine?idea=1717382176223x813221738469654500
It may just be me but I find that I often start out thinking I am going to make a quick fix of build of a backend workflow only to get bogged down as the complexity of what I am trying to do starts to dawn on me. The result is a ton of errors that I know how to fix but other priorities call and those errors stand as a barrier to my launching a new version (yes…if I had thought ahead I would have started a special branch…but as I said… i started out…).
What I have written on the Ideas Board - Please give it a tick mark if you find this is a pain as well
======================================
One can disable workflows on the page, why not in the backend?
The impact is that you either have to
*** 1. complete the entire workflow (if you don’t want to go live without any backend errors)**
*** 2. leave a bunch of errors (confusion in the backend - think recursive workflows - can be costly)**
*** 3. erase a ton of work just in order to go live.**
I recognize that a possible solution is to set up a branch but i find that backend workflows often start out looking like they will take 5 minutes but turn into beasts …arrgghh!!