Conditional Transitions

How Conditional Transitions Work

When an event occurs:

Find matching transitions: Only transitions whose event configuration matches the incoming event are considered.
Evaluate conditions in priority order: A false condition skips that transition. The first transition whose condition is true—or whose condition is empty—is selected.
Run the selected transition: For a transition to another step, run the current step’s On Exit actions, the transition’s Actions, and the destination step’s On Entry actions.

If no transition qualifies, the trainee stays in the current step and no transition actions run for that event.

Setting Up a Conditional Transition

New Transition card showing Events (0), the expanded Condition section with 'Score > 20', and the collapsed Insert Variables section — Condition field containing Score > 20, with Insert Variables below

Select a state and go to the Transitions tab

Click a state, then open the Transitions tab in the Properties panel.

Create or select a transition

Click Add Transition or expand an existing one. Each transition shows Events, Condition, Actions, and Destination Step.

Add an event to the transition

Click the + button next to Events to choose what triggers this transition (Tap, Move, Rotate, etc.).

Expand the Condition section and write your expression

Enter an AXL expression such as Score > 20, as shown in the screenshot. This example uses a Number variable named Score that you have created in the training. Use Insert Variables to reference available variables, and match their names exactly.

Set the Destination Step

Choose the target state from the dropdown.

Optional: Add transition actions

Expand the Actions section and click + to add actions that run during the transition (between onExit and onEntry).

Transition Priority: Multiple Conditions

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. Among transitions matching the event, the first transition whose condition is true or empty is selected. Other transitions are not taken for that event, even if their conditions would also be true.

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. The fallback is selected only when that event occurs and no earlier matching transition qualifies. An unrelated event does not trigger it. Add a fallback when an alternative path is needed. If the trainee should remain in the step until a requirement is satisfied, leave out the fallback.

Transition Actions

In addition to onEntry and onExit actions, transitions themselves can have actions — things that run during the move from one state to another. The event must match and the condition must pass before the transition is selected and its actions run. A Set Variable action on that transition cannot make its own condition pass; record the required value before the triggering event occurs. Execution order:

onExit actions of current state
Transition actions
onEntry actions of next state

Actions start in order. For asynchronous actions, use Wait Until Complete when the next action depends on completion; ordering alone does not guarantee that an animation or audio clip has finished.

Common Transition Actions

Action	Purpose	Example
Set Variable	Save or update a value before entering the next state	Set `completedQuiz` to `true`, or set `score` to `score + 10` to increment
Play Audio	Play a sound during the transition	Play “correct answer” ding
Show Text / Show Panel	Display feedback before the next state begins	Show Panel with body “Nice work!”

Example: Transition Actions

Scenario: Learner taps the correct object. Before moving to “Success” state, increment the score.

Event: Tap correct valve
Transition to: "Success State"
Condition: None (eligible when the event matches)

Transition Actions:
1. Set Variable `correctTaps` to `correctTaps + 1`
2. Set Variable `score` to `score + 10`

onEntry of "Success State":
1. Play Audio: "Excellent work!"

When this transition is selected after the learner taps the correct valve:

onExit of current state runs (if any)
Transition actions run (score increases)
onEntry of “Success State” runs (plays congratulatory audio)

Branching Example: Score-Based Paths

The trainee taps a results button in the scene to see feedback based on their recorded score.

Create a Number variable named score. Use Set Variable actions during the assessment to record the score before the trainee reaches the results step.
In the results step, create three transitions. Configure each with a Tap event targeting the same results button object.
Set the conditions and destination steps below, and arrange the transitions 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:

Score 95: The first transition is selected. Although the second condition would also be true, it is not checked after a transition is selected.
Score 75: The first condition fails and the second passes, so the trainee goes to Good.
Score 60: Both conditions fail, so the fallback sends the trainee to Needs Improvement.

Changing score alone does not trigger these transitions; the configured Tap event must occur. Tapping another object does not trigger the fallback.

Complex Conditions in Transitions

Use the Altoura Expression Language (AXL) to build sophisticated conditions: Each expression below is evaluated when its transition’s configured event occurs. To provide the described alternative path, add a later transition with the same event configuration and an empty condition.

Example: Time-Based Branching

Condition: (now() - trainingStartTime) / 1000 < 60
// If less than 60 seconds elapsed, go to "Fast Completion"
// Otherwise, go to "Slow Completion"

Example: Multi-Variable Conditions

Condition: (score >= 80 && attempts <= 2) || (isAdminUser == true)
// Either (high score + few attempts) OR admin user → go to "Advanced Content"
// Otherwise → go to "Standard Content"

Example: State Tracking

Create these Boolean variables and set each to true when its section is completed.

Condition: hasCompletedSafetyIntro && hasCompletedToolTraining
// Both intro and tool training completed → show advanced scenario
// Otherwise → show basics

Testing Conditional Transitions

Before launching, test all your branches:

Use Set Variable actions to initialize test values, save the training, then Preview and verify each transition. The Variables pane is not a live runtime-value editor.

Test each path

Make sure every conditional transition works. Try different values for each condition.

Test boundary values

If a condition is score >= 80, test with score = 79 and score = 80 to verify the boundary.

Test fallback transitions

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 action execution

Make sure transition actions (like setting variables) actually happen. Check the resulting path or display the values in interpolated panel text after transitions.

Test complex logic

If you use && / ||, test all combinations. For example, if the condition is (A && B) || C, test when only A is true, only B is true, only C is true, etc.

Best Practices for Conditional Transitions

Order conditions from specific to general

Put your most specific conditions first, then broader ones, then a fallback. This prevents unintended paths.

Provide a fallback when an alternative path is needed

Place it after the conditional paths and use the same event configuration. Leave it out when the trainee should stay in the step until a requirement is satisfied.

Keep conditions readable

Avoid overly complex AXL expressions. If a condition is hard to understand, break it into smaller pieces using variables.

Use meaningful variable names

Instead of v1 or temp, use score, correctAnswers, isComplete. Makes conditions self-documenting.

Document your branching logic

Add state descriptions or comments explaining why transitions exist and what conditions control them.

Common Mistakes to Avoid

Expecting a fallback to catch every event: An empty condition does not bypass event matching. Configure the fallback for the same event as the conditional paths. If no transition qualifies, the trainee stays in the current step.

Overlapping conditions: If two transitions both evaluate to TRUE for the same event, only the first fires. Make sure your conditions don’t overlap unintentionally.

Not testing edge cases: A condition like score > 80 works differently than score >= 80. Test both sides of boundaries.

Next Steps

Learn how to:

Use Conditions — Build the logical expressions your transitions need
Create Variables — Store the data your conditions check
Entry & Exit Actions — Coordinate what happens before and after transitions

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

How Conditional Transitions Work

Setting Up a Conditional Transition

Transition Priority: Multiple Conditions

Unconditional Fallback Transitions

Transition Actions

Common Transition Actions

Example: Transition Actions

Branching Example: Score-Based Paths

Complex Conditions in Transitions

Example: Time-Based Branching

Example: Multi-Variable Conditions

Example: State Tracking

Testing Conditional Transitions

Best Practices for Conditional Transitions

Common Mistakes to Avoid

Next Steps

​How Conditional Transitions Work

​Setting Up a Conditional Transition

​Transition Priority: Multiple Conditions

​Unconditional Fallback Transitions

​Transition Actions

​Common Transition Actions

​Example: Transition Actions

​Branching Example: Score-Based Paths

​Complex Conditions in Transitions

​Example: Time-Based Branching

​Example: Multi-Variable Conditions

​Example: State Tracking

​Testing Conditional Transitions

​Best Practices for Conditional Transitions

​Common Mistakes to Avoid

​Next Steps

How Conditional Transitions Work

Setting Up a Conditional Transition

Transition Priority: Multiple Conditions

Unconditional Fallback Transitions

Transition Actions

Common Transition Actions

Example: Transition Actions

Branching Example: Score-Based Paths

Complex Conditions in Transitions

Example: Time-Based Branching

Example: Multi-Variable Conditions

Example: State Tracking

Testing Conditional Transitions

Best Practices for Conditional Transitions

Common Mistakes to Avoid

Next Steps