Concept of what I am trying to achieve / use cases.
The reason that I am attempting to “Isolate” nodes from execute all… I would like to accomplish a “temporary” aspect to component configuration nodes to handle one time actions. Changes to that configuration node’s settings would only effect the next execution run, and then the node would return to its default value state. This would avoid the inevitable errors and hassles caused by forgetting to return a value to its default state after a one time action is necessary.
Current Projects where it would be of benefit:
Open File Location: The setting to activate this should impact the next “execution”. Permanent settings would cause confusion and possible errors from multiple files opening simultaneously on an “Execute All” run.
Revert settings from backup file: The selection of a backup file should only impact the next “execution”. After that, the component settings should return to normal default and continue to operate from the primary source file location.
Email for review: This one time action would send an email with a summary of changes and a notification that a workflow was ready for review.
(The primary approach to this problem can be found here…)