Conditions

When to Use Conditions

Use conditions when your training should respond differently to the same event depending on circumstances. Examples:

Score-based branching: If learner scores >= 80%, show “Congratulations!”. Otherwise, show “Try Again”.
Attempt limiting: If attempts < 3, let them retry. If attempts >= 3, show failure screen.
State tracking: If a tracking variable like safetyTrainingComplete is true, show advanced content. Otherwise, show basics.

Building a Condition

Conditions use variables and operators to create logical expressions. You write conditions directly in the Condition field of a transition using AXL syntax. Create the variables your condition uses and update their values before the triggering event occurs. Conditions are evaluated before transition actions run, so a Set Variable action on that same transition cannot make its condition pass.

New Transition card showing Events (0), an empty Condition field with the placeholder 'e.g., score > 50 && isComplete', Actions (0), and Destination Step set to Step 2 — Empty Condition field showing an example placeholder; no condition has been entered

Open a transition in the Properties panel

Click on a transition to expand it. You’ll see Events, Condition, and Actions sections.

Expand the Condition section

Click Condition to reveal the expression field.

Write your condition expression

Enter an AXL expression such as score > 50 && isComplete, using a Number variable named score and a Boolean variable named isComplete that you have created in the training. Use Insert Variables to reference available variables, and match their names exactly.

Set the Destination Step

Choose where the learner goes when this condition is true.

Operators

Your condition can use these operators:

Operator	Meaning	Example
`==`	Equals	`score == 100`
`===`	Strict equals (recommended)	`score === 100`
`!=`	Not equals	`name != "admin"`
`!==`	Strict not equals	`name !== "admin"`
`<`	Less than	`attempts < 3`
`>`	Greater than	`score > 80`
`<=`	Less than or equal	`remainingTime <= 0`
`>=`	Greater than or equal	`finalScore >= 70`
`+` `-` `*` `/` `%`	Arithmetic	`score + bonus`, `attempts % 2`

Logical Operators: `&&`, `||`, `!`

Combine multiple conditions for complex logic. AXL uses symbol operators only — there are no AND, OR, or NOT keywords.

&& (AND): Both conditions must be true
|| (OR): Either condition can be true
! (NOT): Inverts a condition

Examples

score >= 80 && attempts < 3
// Both must be true: scored well and didn't use too many attempts

selectedOption == "correct" || selectedOption == "acceptableAlternative"
// Either answer is acceptable

!isTrainingComplete
// True if training is not complete

Grouping with Parentheses

For complex logic, use parentheses to control the order:

(score >= 80 && attempts <= 2) || (isAdminUser == true)
// Either (high score + few attempts) or admin user

!(currentState == "locked" || currentState == "disabled")
// Not locked and not disabled

Altoura Expression Language (AXL)

Conditions use Altoura Expression Language (AXL) — a simple expression syntax for building rules. AXL is read-only: you cannot assign values inside an expression. To update a variable with a formula, use the Set Variable action, choose Set Expression, and enter the AXL expression. Choose Set Value to assign a literal value.

Arithmetic in Expressions

Arithmetic can be used in a condition or with Set Expression in a Set Variable action:

score + bonus > 100
(correctAnswers / totalQuestions) * 100 >= 80

For example, in Set Variable, select score, choose Set Expression, and enter score + 10.

Comparisons

score >= 80
finalAnswer == "valve_opened"
attempts < maxAttempts

Logical Operations

isComplete && attempts < 3
selectedLevel == "advanced" || userRole == "trainer"
!isLocked

Ternary Operator (if-then-else)

score >= 80 ? "pass" : "fail"
// If score >= 80, return "pass"; otherwise return "fail"

attempts < 3 ? remainingAttempts : 0
// If attempts < 3, show remaining; otherwise 0

Built-in Functions

AXL provides useful functions:

Function	Purpose	Example
`len(value)`	Length of a string or array	`len(selectedAnswers) == 4`
`clamp(v, min, max)`	Constrain a number between min and max	`clamp(score, 0, 100)`
`now()`	Current timestamp in milliseconds	`now() - startTime > 60000`

Example Expressions

// Count items in an array
len(completedSteps) >= 5

// Calculate time elapsed (in seconds)
(now() - trainingStartTime) / 1000 > 120

To clamp a value, select finalScore in Set Variable, choose Set Expression, and enter clamp(rawScore, 0, 100).

Using Events and Conditions Together

Configure the interaction and target object in the transition’s Events section. Use Condition for additional checks against training variables—for example, score >= 80 or hasCompletedInspection == true. The transition runs only when the event matches and the condition evaluates to true. Leave Condition empty when the matching event alone should trigger the transition.

Transition Priority and Multiple Conditions

When an event occurs, the training checks matching transitions in priority order. The first transition whose condition is true—or whose condition is empty—is selected, and its actions run. Other transitions are not taken for that event. Arrange transitions in Creator with the highest-priority path first. Reordering them sets their evaluation priority. For imported SCJSON with explicit priorities, lower numbers are evaluated first; equal priorities follow document order.

Example: Score-Based Paths

Create a Number variable named score and record the trainee’s score before they reach the results step. Configure all three transitions with Tap on the same results button object, in this order:

Order	Condition	Destination Step
1	`score >= 90`	Excellent
2	`score >= 70`	Good
3	Empty	Needs Improvement

When the trainee taps the results button, a score of 95 selects Excellent, 75 selects Good, and 60 selects Needs Improvement. For a score of 95, both numeric conditions would be true, but only the first transition is selected.

Selecting a Show Panel choice does not automatically assign a variable such as selectedAnswer. For ordinary choice routing, configure each choice’s transition and destination in Show Panel. Add a condition only when that route also depends on data already recorded in the training.

Unconditional Fallback Transitions

A transition with no condition still requires a matching event and must be the first eligible transition. To use it as an “else” path, give it the same event configuration as the conditional paths and place it after them. In the score example, Needs Improvement is selected only when the results button is tapped and neither earlier condition passes. An unrelated event does not trigger that fallback. If no transition qualifies, the trainee stays in the current step and no transition actions run for that event. Add a fallback when an alternative path is needed; omit it when the trainee should remain in the step until a requirement is satisfied.

Testing Your Conditions

Before launching your training:

Use Set Variable actions to initialize test values before the triggering event, save the training, then Preview and verify the selected paths.

Test each branch path

Make sure every condition-based path leads somewhere and works as expected.

Check edge cases

Test boundary values (e.g., exactly 80 when the condition is >= 80).

Verify fallbacks

Trigger the configured event with values that fail the earlier conditions and verify the fallback. Also check that an unrelated event does not trigger it.

Test combinations

If you use &&/|| logic, test all combinations.

Next Steps

Learn how to:

Create and Use Variables — Store the data your conditions need
Variable Types — Understand which type to use (string, number, boolean, etc.)
Conditional Transitions — Combine events, conditions, and actions into complete flows

Creator

Workflow

Transitions

Variables

Actions — Training Control

Actions — Step Instructions

Actions — Media Playback

Actions — Object Manipulation

Actions — UI Control

Actions — Speed & Time

Actions — Training Feedback

Actions — Hand & Tool Visualization

When to Use Conditions

Building a Condition

Operators

Logical Operators: `&&`, `||`, `!`

Examples

Grouping with Parentheses

Altoura Expression Language (AXL)

Arithmetic in Expressions

Comparisons

Logical Operations

Ternary Operator (if-then-else)

Built-in Functions

Example Expressions

Using Events and Conditions Together

Transition Priority and Multiple Conditions

Example: Score-Based Paths

Unconditional Fallback Transitions

Testing Your Conditions

Next Steps

​When to Use Conditions

​Building a Condition

​Operators

​Logical Operators: &&, ||, !

​Examples

​Grouping with Parentheses

​Altoura Expression Language (AXL)

​Arithmetic in Expressions

​Comparisons

​Logical Operations

​Ternary Operator (if-then-else)

​Built-in Functions

​Example Expressions

​Using Events and Conditions Together

​Transition Priority and Multiple Conditions

​Example: Score-Based Paths

​Unconditional Fallback Transitions

​Testing Your Conditions

​Next Steps

When to Use Conditions

Building a Condition

Operators

Logical Operators: `&&`, `||`, `!`

Examples

Grouping with Parentheses

Altoura Expression Language (AXL)

Arithmetic in Expressions

Comparisons

Logical Operations

Ternary Operator (if-then-else)

Built-in Functions

Example Expressions

Using Events and Conditions Together

Transition Priority and Multiple Conditions

Example: Score-Based Paths

Unconditional Fallback Transitions

Testing Your Conditions

Next Steps