Occasionally, when debugging, you may want to disable a workflow without getting rid of it. This could allow you to test specific pieces of functionality without consequent workflows getting in the way, or to modify an existing workflow while keeping a copy of the version that is already working for future reference.
We’ve added this functionality. When you open the property inspector, you’ll see the checkbox beneath “Add a breakpoint in debug mode”.
Is there any difference between this feature and adding a ‘This URL is not empty’ or a “Is development version is no” condition to skip the workflow step?
Just one comment on this (much appreciated!) feature: Twould be nice if disabled workflows INDICATED that in their collapsed views… (rather than having to inspect them).
I just learned that it’s very easy to be comparing workflows and not noticing that one has disabled ALL workflows one was trying to compare.
hinthint
(I expect a rash of forum posts about “MY WORKFLOW NEVER EXECUTES!!! THE BUTTON NEVER DOES ANYTHING!!!” ad nauseum. Excellent feature, though!)
We had a conversation about this earlier today at @luke2’s suggestion, and decided to gray out disabled workflows. This should appear sometime tomorrow.