Events

In Grid Studio an Event is the core element for executing trigger chains. Events can be found in almost every object, device, widget, parameter, cue list, calendar, and many other components.

Just to name a few different events:

  • On message receive

  • On button click

  • On value change

  • On status change

  • On execute cue

  • and so on …

General

Whenever an event is triggered, the green identification in the upper right corner of the node will blink.



Double click on the Event name to rename it.


Object / Device Events

Just drag and drop the device/object into any workflow to get a list with available events.

Besides Object- or Device-specific events like the "Message" Event in this example, there are a few events that are shared by all Objects or Devices:

  • Renamed -> Will be called when the name of the object has changed.

  • Enabled -> Will be called when the object changes the state from disabled to enabled.

  • Disabled -> Will be called when the object changes the state from enabled to disabled.

  • Status Changed -> Will be called whenever the status of the device changed like: Connected, Disconnected, Connection Error, etc..

  • User Data Changed -> Will be called on any parameter change from user defined object parameter.


Parameter Events

Drag any parameter onto the board to generate an event that will be triggered whenever the parameter changes.


Generic Event

It's possible to create your own custom generic events. These events can be triggered from other workflows or from within the same workflow.

A secondary click in an empty space of the workflow opens a menu where you can add a generic event.

Generic events can have their own variables.

Learn more about variables here.

Generic events can be called from action.

Learn more about this here.


Cycle Event

Cycle Event/Timer that repeat endlessly.

Define in the inspector how often these events should be called.


Other Events

In Grid Studio, not all available events come from elements/objects that can be dragged into a workflow.

For example, a single timeline trigger or the event from a single cue list item - just to name a few.

Of course, these elements have their own workflows that are easily accessible. However, if you need to access them from a different workflow, use the Event icon within the Workflow to open the Project menu.

This Icon is the "identifier" for Events

Also a secondary click within the empty space of a workflow can bring you to this list:


Execute Events for testing


Queue Behavior

Each event has its own settings for queue behavior within a workflow:

  • Queue

  • Discard

  • Replace

  • Replace Pending

You can find this setting in the Inspector under the 'Node' tab when the event is selected.

Define here how the execution should behave when it is triggered while a previous instance is still running.

Last updated