Search Knowledge Base



Actions allow you to control and manipulate media, elements, and data in a scene. For example, you can add actions to play a media asset, set a trigger, add value to a counter, show or hide an element. Depending on your settings, actions can occur at specific events. You can add actions to individual scenes or gestures.

Here’s a list of actions you can add to a selected scene or gesture using the Add an Action drop-down menu in the Events & Actions panel or the Gesture Properties panel respectively. For details on individual settings, see Action Menus.

Media Actions

These are the actions that allow you to play the desired media in the demo.

Play Video

Stop Video

Play Sound Effect

Stop Sound Effect

Play Background Music

Stop Background Music

Select to add a respective action to play or stop the media asset that you specify in the action menu.

You can also add the Play Video, Play Music, and Play Sound Effect actions by simply dragging the respective assets from the Assets panel to the canvas. For details, see Add media assets to scenes.


Important: Before adding background music to a scene, in the Assets panel, right-click the file and select Change to background music.

Element Actions

These actions let you display or hide elements in a scene during the demo. They are typically used with triggers and counters when performing logic.

Show Element

Hide Element

Select to show or hide the element specified in the action menu, for example, to make it to appear or disappear in the scene, sometimes after a specified period of time using the At Time setting or after a user interaction (if defined for a gesture). 

For examples of using the Show Element action with triggers and counters, see the use cases in Triggers and Logic-Only Scenes.

Advanced Actions

Use these these actions to define logic in your demo.  See also Advanced Transitions and Logic-Only Scenes.

Set Counter

Select to create a counter and/or set the counter to an explicit value. For instructions, best practices, and other details, see Counters. For use cases, see Logic-Only Scenes.

Add Value to Counter

Subtract Value from Counter

Divide Counter by Value

Multiple Counter by Value

Change Counter by Modulo

Select to change a previously set counter value to a new one using one of the five operators (add, subtract, divide, multiple, modulo). For example, see Use Case 2 in Logic-Only Scenes, where the Add Value to Counter action is used.

Tip: Select any of these options, as the action name updates automatically when you select the desired operator in action menus.

For example, if you select Add Value to Counter and then select Divide in the action menu, the action will be added as Divide Counter by Value. For details on settings,  Counter Action Menus.

Update Text

Select to update text in a previously added Text Area element. For settings, see Update Text action menus.

Update Text with Counter

Select to update text in a previously added Text Area element by using a previously set counter. For settings and value examples, see Text Action Menus. For example, see Use Case 2 in Logic-Only Scenes. See also Counters.

Set a Trigger

Clear a Trigger

Select to add a trigger that you’ll use in a subsequent scene or to clear a previously set trigger after you have used it. For settings, see Trigger Action Menus. For use cases and instructions, see Triggers.

Important: Always clear your triggers after using them.

When to Add Actions to Scenes vs. Gestures

There are two areas in Studio where you can add the actions listed above to your project—the Events & Actions panel and the Gesture Properties panel

As you can see from the images below, the individual settings in the action menus are identical, if you look at the action settings in the red box on the left and the gesture action settings on the right.

Here’s how you decide where to add an actions:

Add actions to individual scenes in the Events & Actions panel, if:

Add actions to the respective gestures in the Properties panel, if:

  • You need to add logic to your actions such as counter and trigger conditionals or use At Time or On Exit events to time actions. For example, see the use cases in Logic-Only Scenes.
  • If there’s no need for either logic or or user interaction
  • You need to execute an action, such as to show an image or play a sound as soon as the user interacts with the screen, for example, by tapping it.
  • You want to stay in the scene without transitioning to another one and do something, for example, to show an element.
  • You want to implement a multiple choice.


Actions Added to Scenes Actions Added to Gestures  
What You Need to Know

Here’s what you need to know when working with actions:

  • All actions are represented by corresponding actions blocks. In the Properties panel, the action block is also the action menu where you define the action settings.
  • To delete an action, delete its action block from either panel. 
  • When you drag video and sound assets to the canvas, the respective action blocks are automatically added in the Events & Actions panel.
  • You can add multiple actions to both scenes and gestures.
  • Don’t add the same action in both panels.
  • In both places, all actions are listed in the order you added them to the scene or gesture.
  • You cannot change the order of actions in either panel.
  • Even though actions are executed in a split of a second, almost simultaneously, they are executed in the order they are listed in the panel.
    In other words, the order of actions does matter, especially in cases, for example, when you need to update a counter value and display it on the screen. If you add the Update Text with Counter action before a Counter action, incorrect value will be displayed.
  • If you select the At Time or On Exit events in the Events & Actions panel, the action list will be automatically reordered to reflect the chronological sequence, with the On Exit actions listed last, before transitions.
  • If you clear these events and set the action to occur On Enter, the action blocks will remain at the bottom of the list where they were moved when you selected the At Time or On Exit events.
  • Transitions always occur last, immediately after actions.
  • Video assets are not added as layers to your project and cannot be hidden. Even when the regular scene sequence is interrupted by a Logic-Only scene, the video player remains in the background, playing the video from the preceding scene, if it has one. If needed, you can do any of the following to end a video:

Was this helpful?

Table of Contents