You are here:
< Back

Available Action Types Based on Event Types

TABLE COMING SOON

Jump to

You only need to specify a page in the content. When this action is executed, the selected page will be loaded in place of the current page.

Next

You don’t need to set up anything else in this popup window, howerver, you will need a next page for this to work. You can either achieve it by adding your pages to the playlist or by manually setting up a next page for all the pages where this action needs to work.

While in some cases it can make sense to have next actions and automatic next page at the same time, usually you would want to turn the automatic option off.

Previous

If you have a playlist put together in the playlist editor, a previous page action will jump backwards in that list.

Popup

A popup is a page of the current content overlayed on top of the current page. There can only be a maximum of one open popup at a time.

Usually popups can be any size (relative to the screen size, e.g. 80% width and 80% height), but external events always open a full size (100% width 100% height) popup. If you need a smaller overlay, set the background of your popup to transparent and add a small box (such as an image or shape widget) wherever you want.

Open/Close/Toggle

You can choose exactly what should happen. Open requires a target page of the content and will always open it, regardsless if there is already an open popup. Close will either close the currently open popup or do nothing. Toggle requires a target page. If the currently open popup is its target page, it will close it. In any other case, it will open the target page as popup.

Close Time

If you turn on the auto close option and add a popup duration (in sec), the popup, if still open, will be closed after the set amount of time.

Call API

Your Request

The request will always be called as “POST”. If you need path variables or request params, you can type them in the url field. Request body will depend on the external event type, for example, for a sensor event, it will contain “event”, “id” and sometimes “value”. For a simple case of API call as a click type on an interactive image widget, it will have “event name” and “event value”. Read more about these in the respective guides!

API Response Actions

If you only need one-sided communication, you don’t have to worry about the response. However, if you also need the content to change, your response has to follow some simple rules:

  • A request always has to have a fix, string or number type property in the response. It can be any field, but it has to be the same.
  • Any property you want to handle later has to be in a compatible type with the selected action.

If your always present property is called “responseCode”, you will need to type that to the main property name field. Then, in the main property value column you can set up rules for different scenarios.

If you only need to jump to a different page or always want to open a popup, you don’t need anything else. In case you want to change the value of a widget (text, image, etc) you also need to specify a property for that. This property has to be compatible with the widget and always has to exists when, based on the main property value, this action will be executed.

Static Sensor Event

If this action gets executed, the output text will be sent to all the connected sensors which are listening for it.

Dynamic Sensor Event

A dynamic sensor event will just send whatever it triggered it towards the sensors. If any connected sensor can handle that, it will. If it came from an API call, it will send the whole response. If a datasource event, it will wrap the value in an object like this: {value: 3}.

Show/Hide Widget

You can select a widget from any page in the content. You can also specify whether it has to be shown, hidden or toggled.

Interact Widget

You can interact with usually interactive widgets (such as checkboxes) and widgets that can handle data binding (such as texts). Some external events (sensor, datasource events) can only interact with a subset of these.

Usually Interactive Widgets

These work the same way for all applicable external event types.

Checkbox

A checkbox can be checked, unchecked or toggled between these two states. Any identical checkbox will follow this change as usual.

Radio Button

A radio button can only be checked. Any other radio button in the same button group will be adjusted as usual. Identical radio buttons will become checked, others unchecked.

User Input

A user input can be either overwritten with the recieved text or it can be appended to the current content of it. Also, based on the external event type, you may need to specify a property name or a value.

  • For sensor events, you can leave that field empty, the event value of the sensor will be used.
  • For datasource events, you can also leave that field empty, the value that triggered the change will be used.
  • For API response events, you need to specify the propety name of an applicable field (text or number).
  • For touch actions, you need to type the actual value that you want to see.

Reset Button

A reset button doesn’t have any special options. It will trigger the selected widget as if it was pressed by the user.

Submit Button

A submit button doesn’t have any special options here, however, if there are submit type properties and touch actions set up for the targeted widget, they will be executed.

Carousel

A carousel can be flipped through backwards or forward. Right now, it is just to let your user flip through images, but in the future it may be possible for an action to take into consideration the currently selected image, as if it was similar to a radio button group.

Data-bind Capable Widgets

You can push a value to a data binding capable widget just as if it came from a datasource. You don’t even need to connect them to a datasource first for this to work. Select a widget, such as text or image and give it an applicable value. For a text, it can be any string or number value. For an image, it has to be either a valid image source url or the file name of an uploaded picture, as if it was actually bound to a datasource.

  • For API response actions, you need to specify the property name of a field in your response
  • For touch actions, you need to type the actual value.

Content Widgets

Two types of content widgets can be interactived with.

  • If a loop is selected, it can be paused, resumed or toggled.
  • If it is a content, and the one page option is turned on, all of the interactive widgets inside that one page will be added to the list of possible target widgets.

Ignore

Ignore won’t do anything. It’s purpuse is to block other actions from doing anything. If it is not final, it will only block the fallback action. If it is final, it will block any other action that cames after it in the actions list. If there are both page wide and content wide actions for the external event type, page wide actions will be interpreted first, so a page wide final ignore action will block all content wide actions as well.