Skip to main content

Variable triggers

The variable trigger triggers a flow when the value of a global variable changes.

 Variable Trigger

PropertyDescription
Trigger Data PointA global variable whose change triggers the transfer. Selecting this option opens a tree view of global variables with their folders and data types. Metric variables (aggregations) can also be selected; they trigger when the window value changes—two identical windows in succession do not trigger the transfer.
No more than

If the value of the data point changes frequently, you can use this setting to limit the number of transfers per interval. This setting means: “Data is transferred at most, for example, once per second, even if the value changes more frequently.”

Always enter a whole number; do not include decimal places. Therefore, select milliseconds, seconds, minutes, or hours as the units.

At least everyTime interval during which data is transferred regardless of whether the value of the data point has changed. The default is always a whole number; no decimal places are allowed. Therefore, the units must be milliseconds, seconds, minutes, or hours.
Trigger at ... % differenceThe transfer is triggered only if the value of the data point changes by this amount (relative).
Triggers Based on Absolute DifferenceThe transfer is triggered only if the value of the data point changes by this amount (absolute).
Triggers on Exact ValueExecutes the flow if exactly one value is present.
Trigger on every data changeDefault setting; overrides triggers when the difference is ...

Trigger behavior​

Diagram of the variable trigger with trigger variants

The diagram shows the trigger behavior on a change of an internal variable – analogous to the data-change trigger.

Templates​

 Variable Triggers

In a template, you can specify the trigger data point as a template variable instead of selecting a specific value: The “Template variable” toggle displays a path field that can contain placeholders (e.g., {Anlage}/Temperatur) or be bound to a template variable. Each instance then monitors the variable to which its resolved path points.