Using Entities in Workflows

Entities can be used directly inside Workflows to react to data changes or to read and write values.

The easiest way to create entity-based workflow nodes is by dragging an entity entry directly into the Workflow Editor.

Depending on where the entity is dropped, Grid Studio automatically creates the appropriate event or action node.

A workflow event can be created by dragging an entity value from the Entities view into the Workflow Editor.

This creates a Value Change Event that triggers whenever the selected entity value changes.

The event provides the current value as part of the event data, allowing the workflow to react to changes of that specific entity.

This is commonly used for reacting to device status changes, sensor values, or other dynamic system data.

In addition to value-specific events, workflows also support Object Entity Value Change events.

This event listens to all entity value changes of an object.

Whenever any entity value changes, the event is triggered and provides additional information including:

This allows workflows to react to dynamic or unknown entity structures where the specific entity path may not be known in advance.

Workflows can also read or modify entity data using actions.

Several actions are available for working with entity values and datasets.

These actions operate on a single entity value.

This is commonly used when workflows need to read or modify individual values.

These actions operate on entire entity structures rather than individual values.

They are typically used when working with parent entities that contain multiple child entries.

This allows workflows to process or replace larger structured datasets.

Last updated 2 days ago