that’s exactly what i’ve done in a component.
But whenever i want to bypass some nodes in my development workflow i’ve to:
-drag in my component
-cut and paste the nodes i want to bypass on in
In this scenario i can simply disconnect the nodes and bypassing them the easy way, we should be able to do that with a simple toggle when converting a bunch of nodes into a component or metanode
Empty Table Switch is a good solution if you only have to handle empty tables. If you have to handly more complex states you can control the If Switch Node with a Rule Engine Variable. If your conditions are true then use the “top” output of the If Switch otherwise the “bottom” output.
Of course you can nest these switches.
If we are looking for something that can be configured easily to enable or disable part of a flow without having to disconnect nodes, then maybe something like this is a workaround? It cannot do pass-through, but it can do disabling.
Would be interested in feedback. Are there situations where this won’t work? Does it cause any problems? It makes use of the “Fail in execution” node to fail a flow within the component if “Disable Flow” has been chosen.
Taking this further, and utilising the If Switch concept, but making it into something that visually identifies this as a specific “Bypass” and also making it simple to turn on and off. Here is a bypass component. Under the surface, its really just an IF switch and a variable, but it can be configured easily to bypass or not .