Actions
An action ties an event on a screen — a touch or connected-device signal — to a player response, such as advancing to the next item or jumping to a specific layout. Actions are how you build interactivity on touch screens, kiosks, and integrated installations.
Get there: sidebar → Actions
How an action works
Section titled “How an action works”Each action has two halves:
- Trigger — what fires it: a touch event or signal from a connected device.
- Target — what the player does in response: play next, play previous, jump to a layout, or run a command.
When the trigger condition is met on a screen, the player runs the target. A typical use: a touch-screen kiosk where touching anywhere advances to the next product page. That’s a single action with a Touch trigger and a Next target type, attached to the layout.
What you see on the page
Section titled “What you see on the page”| Column | What it shows |
|---|---|
| Source | The layout, region, or widget the action is attached to |
| Trigger | The trigger type — touch or navigate |
| Trigger Code | Optional label used by connected-device triggers |
| Action | The target action type |
| Target | The target object, if any |
| Layout Code | The destination layout code, for navigate actions |
Right-click a row for Delete. Tick checkboxes to enable a bulk Delete (N) button.
Sources
Section titled “Sources”An action is attached to one of three source types:
| Source | Scope |
|---|---|
| Layout | The whole layout — touch anywhere triggers the action |
| Region | Just the region — touch within the region triggers it |
| Widget | A specific widget inside a region |
Choose the layout, region, or widget the action should listen to.
Trigger types
Section titled “Trigger types”| Trigger | Fires when |
|---|---|
| Touch | The viewer touches or clicks the source on the screen |
| Navigate | The player receives a navigation signal from a connected device, such as a barcode scanner or remote control |
The optional Trigger Code identifies which navigation signal the action listens for. Two actions on the same layout with different codes can do different things.
Action types
Section titled “Action types”| Action | What the player does |
|---|---|
| Next | Advance to the next item in the region’s playlist |
| Previous | Go back to the previous item |
| Navigate | Jump to a specific layout, identified by its layout code |
| Code | Run a player command |
Create an action
Section titled “Create an action”- Click the + button (tooltip: New Action).
- On the Trigger tab:
- Source type — Layout, Region, or Widget.
- Source — choose the layout, region, or widget.
- Trigger Type — Touch or Navigate.
- Trigger Code — optional, for navigation triggers.
- Action Type — Next, Previous, Navigate, or Code.
- Switch to the Target tab if the action needs a destination:
- Target type — Layout, Region, or Widget (Navigate actions only).
- Target — choose the destination.
- Layout Code — destination layout code, for navigate-to-layout.
- Click Create Action.
A help-mode toggle in the dialog header reveals inline tips on each field.
Delete an action
Section titled “Delete an action”Right-click → Delete and confirm.
For bulk delete, tick the row checkboxes and click Delete (N) in the toolbar. A confirmation dialog asks you to confirm.
A worked example
Section titled “A worked example”To advance a touch-screen kiosk to the next page when touched anywhere:
- Source: Layout, choose the kiosk layout
- Trigger Type: Touch, Trigger Code: blank
- Action Type: Next
Save. From now on, any touch on a screen playing that layout advances the playlist.
Permissions
Section titled “Permissions”The page appears only when your role includes action access. Create and delete buttons appear based on your action permissions.