Customers building flows may want to test what happens if they remove / disable an action / group of actions from a flow, but they may only want to do this temporarily during testing.
As flows become more advanced, it may be useful to allow the disabling of actions / group of actions, while retaining the configuration made within them (so that they can be simply re-enabled rather than recreated later).
As part of this, we must make sure it is clear and obvious within the flow development environment what actions are disabled and will be skipped.
Thought: Using above functionality, is there value in having disabled 'template' flows in the system? i.e. unvalidated flows that serve as examples that can be copied and susequently enabled with required values?
The reason this is a thought rather than a request as such is I'm not sure of the level of validation in all potential 'template' scenarios - i.e. whether validation prevents saving of such flows currently, so may be moot. We'll get a better idea when we try to formalise some of the 'functions' we want as project flows.