ATLAS FormBuilder - Logical Operators in Conditional Statements

This tutorial gives an in-depth explanation of how logical operators are used in FormBuilder's conditional statements.

Conditional statements are found throughout FormBuilder's settings, from routing trigger conditions to optional filtering on aggregate form views (to learn more, visit ATLAS FormBuilder - Introduction to Conditional Statements).

These statements involve selecting conditions from a wide list of options -- most of which allow for some degree of customization -- in order to form the logic upon which the setting will be evaluated. Each conditional statement only allows for the selection of one condition by default, but multiple conditions can be chained together to form more complex logic through the use of logical operators.

Logical operators are selected from the same dropdown list of options as other conditions. Unlike other conditions, logical operators do not provide their own customizable fields, but instead allow for the addition of sub-conditions (aka. "child" conditions) -- often multiple at a time -- which it then acts as a "parent" for. These sub-conditions can even include more logical operators.

The available operators and their functions are as follows...

And - Allows for the addition of multiple child conditions, which it links together as an "And Group." When the conditional statement is being evaluated, an And Group will only be considered true if ALL conditions contained within it are true. Otherwise, it will be considered false. 

The "And" logical operator selected as a condition for a routing trigger, with two different "child" conditions.

Or - Allows for the addition of multiple child conditions, which it links together as an "Or Group." When the conditional statement is being evaluated, an Or Group will be considered true if ANY of the conditions contained within it are true. It will only be evaluated as false if all of its child conditions are false.

The "Or" logical operator selected as a condition for a routing trigger, with two different "child" conditions.

Not - Allows for one child condition. When the conditional statement is being evaluated, a Not operator is only considered true if its child condition evaluates as false.

The "Not" logical operator selected as a condition for a routing trigger, with one "child" condition.

Any of these three logical operators can be combined in different ways to create more complicated conditional statements. As you get used to working with logical operators, try using them in conjunction with one another to further specify the logic of your form's settings!

A routing trigger's trigger condition that uses a combination of logical operators, with a parent operator of Or, and a child statement that uses the Not operator.


For more articles and tutorials about ATLAS FormBuilder, visit FormBuilder - Homepage.



Keywords:
atlas, formbuilder, conditional, statement, and, or, not, routing, trigger, phase, logic, logical, operator, condition, setting 
Doc ID:
81896
Owned by:
Beckett A. in University of Illinois LAS
Created:
2018-04-25
Updated:
2024-12-12
Sites:
University of Illinois Liberal Arts and Sciences