Using conditionals steps in the mabl trainer

Within the mabl trainer, you can add conditional steps inside Journeys where IF, ELSE, and END steps are available to run groups of steps or flows conditionally. Conditionals can include any number of steps or flows and can also be used within a reusable flow.

Adding conditionals

While in the mabl Trainer, navigate to the "More Actions" menu in the bottom right.

In this menu, find and click the "Add Conditional" option. Now you can begin adding conditional steps.

To form a complete conditional statement, you will need to include all of the following:

IF

You'll need to add an IF statement first. When you select "IF", you'll be prompted to select a conditional to base the statement on, which can be any of the following shown below:

Just like a regular IF statement, whatever conditional you select must be true for the steps within the IF statement to run.

Once the IF statement is added, record steps like you normally would to add them to the IF statement. Once you're finished adding steps, you'll need to add an ELSE and END statement.

ELSE

After adding your IF statement, you'll need to add an ELSE statement in the event that your conditional is false. Simply repeat the steps above and select "ELSE" instead of "IF".

You'll see an ELSE step show up in the trainer now, be sure that it is located at least one step after the IF step. Now you can add whatever steps you would like for the ELSE statement. You can also leave this empty, if you would like.

END

Now that you have your IF and ELSE statements added, you'll need to add an END statement. Follow the same steps above, selecting "ELSE" instead of the other two options. You'll see the END statement added in the trainer window. Again, be sure this is located after the IF and ELSE statements.

More information

Any steps not executed during a Journey run due to a conditional will show up in the Journey output logs as a greyed out step with the indication it was skipped.

Using conditionals steps in the mabl trainer


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.