Skip to main content
Back to path

Welcome to a Grasp lesson

Create a free account to keep studying and create your own study path.

Lesson 24

Conditional Visibility with the Condition Tool

Recommended resources

Hello! Welcome back to our series on Alteryx Analytic Apps.

In our last lesson, we explored the powerful Action tool, learning how to connect user inputs to our workflow's logic and dynamically update tools. We saw how it acts as the brain of an analytic app, translating user choices into specific instructions.

Now, we'll take that concept a step further. A well-designed app not only responds to user input but also guides the user by presenting only relevant options. Imagine an app where selecting "Advanced Mode" reveals a new set of questions, or choosing "Standard Report" hides all the custom formatting options. This creates a cleaner, more intuitive user experience.

Today's lesson focuses on exactly that. You will learn to implement conditional logic to show or hide interface elements using the Condition tool. This is a fundamental skill for building professional, user-friendly analytic apps and a key topic for the Alteryx Advanced Certification.

The Logic of a Dynamic Interface: The Condition Tool

The key to creating a dynamic interface is the Condition tool. You can find it in the "Interface" tool palette. Think of it as an if-then-else statement for your app.

It's a simple but powerful tool with one input anchor and two output anchors:

  • Input: It accepts a connection from another Interface tool (like a Check Box, Radio Button, or Drop Down).
  • True (T) Output: If the condition you define is met, it sends a signal out of this anchor.
  • False (F) Output: If the condition is not met, it sends a signal out of this anchor instead.

You configure the Condition tool by writing a simple expression that evaluates the input from the user. For example, if you have a Check Box tool, its output is either "True" or "False". Your Condition tool's expression might be [#1] == "True", where [#1] refers to the incoming connection from the Check Box.

The Core Pattern: Condition, Action, and Containers

To show or hide a group of interface questions, you need to combine four tools in a specific pattern:

  1. Interface Tool: The user makes a choice (e.g., clicks a Radio Button).
  2. Condition Tool: Evaluates the user's choice.
  3. Action Tool: Takes the signal from the Condition tool's 'T' or 'F' output.
  4. Tool Container: Holds the group of interface elements you want to show or hide.

The magic happens when the Action tool, triggered by the Condition tool, disables the Tool Container that holds the irrelevant questions.

Let's look at a complete, practical example of this pattern.

Alteryx Analytic App Workflow with Conditional Logic
This image shows a perfect implementation of conditional logic. On the right, the app asks the user to choose 'Standard' or 'Non-Standard'. The workflow on the left implements the logic to handle this choice.

Let's break down the workflow in the image:

  1. A Radio Button tool asks the user to select the duration type.
  2. The output is fed into a Condition tool. Let's assume the condition checks if the user selected "Standard".
  3. If True (user chose "Standard"), the 'T' anchor fires an Action tool that is connected to the 'Not Standard' container. This action disables the "Not Standard" container, hiding its questions.
  4. If False (user chose "Non-Standard"), the 'F' anchor fires a different Action tool connected to the 'Standard' container. This action disables the "Standard" container, hiding its questions.

The end result for the user is a clean interface that only shows the options relevant to their choice, as seen on the right side of the image. By default, you would have both containers enabled in the Designer canvas, and the app logic takes care of hiding one at runtime.

This pattern of disabling what is not needed is the standard way to build conditional interfaces in Alteryx.

Here is another, simpler example using a Check Box.

Alteryx Workflow for Conditional Container Logic
In this workflow, a Check Box (12) likely determines whether a 'Weekly' or 'Monthly' report is desired. The Condition tool evaluates this choice and triggers an Action tool to enable or disable the corresponding containers.

The Specific Action Type

When you connect a Condition tool's output to an Action tool, and then connect that Action tool to a Tool Container, Alteryx is smart enough to select the correct Action Type for you: Enable/Disable Container from Condition Tool.

Let's confirm this by looking at the official documentation. In the previous lesson, you skimmed the list of Action Types. Now, let's focus on the one that's relevant today.

Action Tool - Alteryx Help

The Alteryx Help documentation for the Action tool provides a concise description of this functionality. Please read the specific entry for conditionally managing containers.

In the table of Action Types, find the row titled 'Enable/Disable Container from Condition Tool'. Note the example connection path given: Radio Button Tool > Condition Tool (T) > Action > Tool Container Tool. This confirms the exact pattern we've been discussing.

Building It Yourself: A Mini-Tutorial

To solidify your understanding, let's walk through the steps to build a simple conditional interface.

  1. Start a new workflow. Drag a Tool Container onto the canvas. Inside it, place a Text Box interface tool and label it "Enter Custom File Name".
  2. Drag a Check Box tool onto the canvas (outside the container). In its configuration, set the "Label" to "Use Custom File Name?".
  3. Drag a Condition tool onto the canvas. Connect the output of the Check Box to the input of the Condition tool.
  4. Configure the Condition tool. In the "Expression" box, write [#1] == "True". This means the condition will be met if the user ticks the box.
  5. Now, the crucial step. By default, you want the custom text box to be hidden. Select the Tool Container and check the "Disabled" box in its configuration pane.
  6. Connect the 'T' (True) output of the Condition tool to the input of an Action tool.
  7. Connect the output of that Action tool to the Tool Container.
  8. Select the Action tool. Its "Action Type" should be automatically set to "Enable/Disable Container...". This action will now enable the container when the box is checked, overriding its default disabled state.

Now, if you run the workflow as an Analytic App, you will see that the text box is initially hidden. When you check the box, the text box for the custom file name will appear.

Conclusion

In this lesson, you've learned how to elevate your Analytic Apps from simple forms to dynamic, interactive experiences. By mastering the Condition tool, you can guide users through a workflow, showing them only the questions that matter based on their previous answers.

Key Takeaways:

  • The Condition tool is the core of interface logic, acting as an if-then-else switch based on user input.
  • The primary pattern for conditional interfaces is: Interface Tool → Condition Tool → Action Tool → Tool Container.
  • The Action tool's role is typically to disable the container holding the interface elements that are not relevant to the user's current selection.
  • This technique is essential for creating clean, uncluttered, and user-friendly applications.

In our next lesson, we will continue to build on our app design skills by exploring how to implement user input validation and create custom error messages using the Error Message tool. This will help you build more robust and foolproof applications.