Topics Map > ATLAS Applications > ATLAS Formbuilder

ATLAS FormBuilder - Conditional Statements in Routing Triggers

This tutorial gives a more in-depth explanation of how conditional statements are used in routing triggers.

Routing triggers can form a chain of events, send emails, and move your form forward.  For more information on building routing triggers, check out ATLAS FormBuilder - Lifecycle - How to Build a Routing Trigger.

A common mistake administrators make when building their form is that they include conditional statements within routing triggers that are not specific enough.  For a form to function properly, each phase needs to be defined specifically by these routing triggers, and that sometimes means creating multiple routing triggers with these conditional statements to get the job done.  

For example...

1.) If a specific question needs to be answered before the form changes phases, but the only routing trigger put into place is one that changes phase when the form is submitted, this will not be possible because the phase will move on without the question being answered. In this scenario, it will be useful to use the 'And' option - the form needs to be submitted and  the question must be answered for the form to change phases. 

Below you can see how that scenario looks using the conditional statements available to you.

2.) The 'Or' option for a conditional statement is useful for joining together two possible situations that will ultimately lead to the same outcome.

The example below shows how you can use the 'Or' statement to place these distinctions within the same routing trigger.   This is useful if you want form responders who are already registered to receive an email update and you also want the form responders who have been placed on the waitlist to receive the same update.

3.) The 'Not' statement can be useful for defining when you want a routing trigger to take effect.

For example, 'Not' is especially useful for keeping track of payments.  You may want to send a reminder email to each form responder with a status of Unpaid, Partially Paid, or Refunded. Using 'Not' is a great way to catch everyone that might still need to submit a payment for their form to be fully processed.

For more information on how conditional statements are used in other parts of the form-building process, take a look at ATLAS FormBuilder - Introduction to Conditional Statements.