Skip to main content

Variable Transfer Object

You use the Variable Transfer Object to read and write the variables of the Variable Plug-in within the flow. User-defined variables are available as both sources and destinations, while system variables and metric variables (aggregation) are available as sources.

Variable Transfer Object

The dialog displays two tabs—“Global variables” and “Local variables”—showing the respective number of variables used. For each tab, a tree view lists the variables used, grouped by folder:

ColumnDescription
Variable PathVariable with folder structure. Resolved variables are read-only here; the name is maintained via the variable editor.
TypeData type of the variable.
ValueCurrent value (only for global variables). Secrets are displayed masked.
ActionsEdit variable or remove row. Click the column header to remove all rows from the tab.

Add variables using the buttons in the dialog:

  • Select Variables opens the variable selection dialog: a filterable tree view of all variables in the current scope that have not yet been used. Check the desired variables and apply them by clicking “OK”. Checking a folder’s checkbox selects all variables it contains; if one of them is deselected, the folder displays a partial state.
  • New Variable creates a new variable directly from the transfer object. This opens the Edit dialog of the Variable Plug-in .

Templates​

Variable Transfer Object

In a template, the “Template variables” section appears above the tree view. There, you define variable paths that are resolved on a per-instance basis: The path can contain placeholders (e.g., {Anlage}/Temperatur) or be directly bound to a template variable. At runtime, each instance reads or writes the variable to which its resolved path points. Paths that cannot yet be resolved remain editable in the line.