If you’ve ever found it challenging to manage the sequence of operations in your workflows, the Control Container tool can make things easier!
Why Use Control Containers?
Curious about how this tool fits into your workflow and what it can do for you? Let me share three significant advantages you need to know:
- It makes sure events follow the right sequence when needed.
- You can organize your workflow, it allows you to write multiple outputs in a preferred sequence.
- It’s simpler to design complex workflows without having to understand advanced topics like batch macros and chained apps.
So, you’re still not using it?
But what exactly is it?
Control Containers allow for conditional execution of specific logic blocks, depending on data from the workflow, other Control Containers, or various tools. This helps create more dynamic and complex processes.
To guarantee that one process doesn’t begin before another has completed, it’s important to use multiple Control Containers.
AMP Only
If the AMP engine is turned off, using the Control Container tool in your workflow will result in an error.
How to make it work?
The workflow failed due to an incorrect connection of the Control Containers.
Below you can see how to properly set it up to make use of the control containers’ functionality.
If the Control Containers in your workflow aren’t connected, the desired result won’t be achieved, and an error will appear. This is demonstrated in the GIFs above. The first GIF shows the outcome when the containers are not properly connected, while the second demonstrates the correct setup.
To join two Control Containers, you should follow steps similar to those used when adding and connecting a new tool within a workflow.
2 Anchors: Control Input (Optional) vs Logging Output
Control Input (Optional)
Think of the Control Input as the starter button for your Control Container. When a record arrives, it’s like pressing that trigger to start the process. Once activated, the container waits for all records to pass through this point before beginning its core tasks. This design ensures everything is ready before the main work begins.
What happens if there’s no connection to the Control Input? It’s simple! The container activates and works in a similar way to a Tool Container.
The Logging Output
The Logging Output is like having a conversation about what’s happening inside the container. It captures every detail, showing all the log messages from the tools inside, including any sub-containers. These messages only appear in the Control Container data if they’re also visible in the Results grid, ensuring that only the relevant information is displayed.
But what happens if the container is disabled? In that case, it stays silent—no messages are generated. This helps keep your workspace free from unnecessary data when the container isn’t in use.
What about the configuration?
- Similar to a Tool Container, you can use a Control Container to group tools. When you move the Control Container, all the tools inside it move as one unit.
- It automatically adjusts to create space whenever you add more tools.
- Additionally, you can customize the appearance of your Control Container. You can choose different colors for the text and borders, modify the background color, and even adjust its transparency. You can also resize it to suit your preferences.
Disabled Control Container vs. Enabled Control Container
Disabled: Designer ignores the container (as well as all tools within it) and it won’t report any configuration errors for them either.
Enabled: Designer decides whether to activate it depending on the records received by the input anchor when the workflow is executed.
Limitations
Control Containers offer great flexibility and are compatible with various tool types in Alteryx. For instance, In-Database tools work seamlessly inside Control Containers. Detour Tools also integrate smoothly, though if a Detour End tool is placed inside an inactive Control Container, the data stream is dropped. Control Containers can also be efficiently used within macros.
However, some tools are not compatible:
- Interface tools are not supported inside Control Containers.
- Block Until Done (BUD) tools are also unsupported and will trigger an error.
- Looped connections generate an error.
- A Debug Workflow containing Control Containers will result in an error.
Understanding these limitations can help you better plan and execute your workflows, avoiding unexpected interruptions.
In Conclusion
Control Containers are a fantastic way to make your Alteryx workflows more efficient. Whether you’re dealing with large datasets or complex sequences, they help ensure everything runs smoothly.
