Controlling Transitions with Conditions and Action Chains
This page walks you through implementing a conditional automatic transition for the DetailView, combining a timer with a checkbox value. The central concept here is the division of roles: the Action Chain Editor is where you build the processing flow, and the Condition Editor is where you independently define condition expressions. You will create a behavior that returns to the MainView after a certain amount of time has elapsed since entering the DetailView, while stopping that automatic transition only when the KeepDetailOpenCheckBox is checked. This lets you understand in practice how Triggers, Conditions, and Actions work together. In particular, setting the OperationMode of Check Processed Value to CompareExternalValueWithConditionValue is the key to correct operation on this page.
Configuring the CheckBox Control
First, convert the state of the CheckBox control placed in the DetailContent scene into a form that the Condition Editor can read. If you skip this step, you cannot use the current check state within a condition expression.
- Double-click the DetailContent scene to open the Scene Editor.
- Select KeepDetailOpenCheckBox in the Scene Tree.
- Drag and drop a Forward Value behavior onto the Extra Scene Tree.
- Select the Forward Value behavior you just added and configure the following properties in the Properties panel:
Property Category Item Value Asset EventDispatchStrategy DedicatedBehavior - Add a Value behavior under the DedicatedBehavior node of the Forward Value behavior.
- Drag and drop the Value behavior you just added onto the DetailContent scene in the Scene Tree to associate it.
This configuration causes the CheckBox control's current value to be held on the scene node side, making it available to the Condition Editor as an external value. The Value you created here is the target you will specify as the ValueBehavior in the next step.
Configuring the ConditionBlock
Here, you define the condition logic that determines whether the automatic transition is allowed, separately from the Action Chain. By isolating the condition, you can understand the processing flow and the evaluation logic independently.
In this task, you create a condition that evaluates to true only when both the timer has fired and the KeepDetailOpenCheckBox is unchecked. This is the heart of the conditional transition.
- Select the Solution folder in the Solution Explorer, then select Add > New Item from the context menu.
- Select ConditionBlock from the New Item dialog and name it ReturnToMainOnTimeoutCondition.
- The Condition Editor panel appears, displaying the diagram for the newly created ReturnToMainOnTimeoutCondition > Condition.
- The Condition Editor panel appears, displaying the diagram for the newly created ReturnToMainOnTimeoutCondition > Condition.
- Right-click the diagram and select Add Check > Condition > Control > Check Timer to add it to the diagram.
- Similarly, select Add Check > Condition > Control > Check Processed Value from the context menu to add it to the diagram.
- Select the Check Processed Value you just added and configure the following properties in the Properties panel:
Property Category Item Value Asset OperationMode CompareExternalValueWithConditionValue ConditionOperator Equal ConditionValue type Bool ConditionValue False ValueBehavior DetailContent scene > Value - Next, select Add AND from the context menu to add an AND node.
- Connect Check Timer and Check Processed Value to the AND node.
- Connect the output of the AND node to ConditionOutput.

The condition created here means: allow the automatic transition only when the timer has fired and the checkbox is unchecked. The OperationMode setting is particularly important. If you set this to a processed-event-dependent mode such as CompareProcessedValueWithConditionValue, no value event exists for comparison at the time of the Timer event, and the condition cannot be evaluated correctly. The correct choice here is CompareExternalValueWithConditionValue, which references the external value held on the scene node.
Configuring the DetailView On Entry Setting
Next, you configure a setting that starts a timer the moment you enter the DetailView. No transition occurs at this point; this step only establishes the reference time for the subsequent condition evaluation.
- Double-click MainViewTree to open the View Tree panel.
- Select DetailView and configure the following properties in the Properties panel:
Property Category Item Value State OnEntry > Action Start Timer OnEntry > Delay 3000
This setting means that 3 seconds after entering the DetailView is used as the timing for the automatic transition evaluation. Note that starting the timer and performing the transition itself are separate configurations.
Configuring the Action Chain
Finally, you build the processing flow that receives the timer firing, evaluates the ConditionOutput, and returns to the MainView only when the result is true. This is where the Action Chain Editor and Condition Editor work together for the first time.
-
Double-click MainViewTree to open the View Tree panel.
-
Double-click DetailView to open the Action Chain Editor.
-
Double-click ActionChain1 in the left pane to open the diagram.
-
Right-click the diagram and select the Condition of the previously created CloseMenuOnTimeoutCondition from Add Condition to add it.
-
Select Add Action > Action > Views > Jump To View from the context menu and place it on the diagram.
-
Select Jump To View and configure the following properties in the Properties panel:
Property Category Item Value General Name JumpToMainViewAfterTimeout Asset View MainView -
Select Add Trigger > Condition > Control > Check Timer from the context menu and place it on the diagram.
-
Connect Check Timer and Condition on the diagram.

-
Finally, snap the **Jump To View** action to the **Condition** to connect them.

This configuration means: when the Check Timer fires, the system evaluates the ConditionOutput of ReturnToMainOnTimeoutCondition, and if the result is true, returns to the MainView. If you connect Check Timer and Jump To View directly, the system always returns after the timer elapses, and cannot reflect the checkbox state. By placing the ConditionOutput in between, the transition becomes conditional for the first time.
Verifying the Behavior in the Player
This verification confirms not only the automatic transition triggered by the timer, but also that the behavior changes depending on the checkbox state. This is the final check to ensure that the division of roles between the Action Chain and the Condition is functioning correctly.
- Save the solution and start the Player.
- Verify that the MainView appears immediately after startup.
- Verify that the MainView appears immediately after startup.
- Click Open Detail.
- Verify that the display switches to the DetailView.
- Verify that the display switches to the DetailView.
- Leave the Keep Detail Open checkbox unchecked and wait 3 seconds.
- Verify that the display automatically returns to the MainView.
- Verify that the display automatically returns to the MainView.
- Click Open Detail again.
- This time, check the Keep Detail Open checkbox.
- Verify that the display does not automatically return even after approximately 3 seconds.
- Verify that the display does not automatically return even after approximately 3 seconds.
- Verify that you can return to the MainView by clicking Back.
On this page, you used the Action Chain Editor and the Condition Editor together to implement a conditional automatic transition whose behavior changes depending on the UI state. With this, you have practiced all four basic functions of the View Editor: creating screen-level Views with the View Definition Editor, structuring their relationships with the View Tree, building processing flows with the Action Chain Editor, and isolating condition expressions with the Condition Editor. This completes the entire tutorial series.