Binding Target

The binding target is an object affected by the binding. It can either be a widget component or some data within a Iotellect Server context. To affect a widget component, the binding target has to point to one of its properties. To modify context data, the binding target has to point to a context variable, field of a variable or the input field of a context function (see server binding target).

In fact, the binding target is a special type of reference. Two types of binding targets are supported: one with no schema (and thus, no prefix), which points to context data, and another, which uses the form schema and prefix (form/) and points to the widget component properties.

Widget binding targets support all syntax variants of server binding targets.

The following additional syntax variants are supported:

form/component:property

This binding target points to a specific property of a widget component.

Binding target that refers cell of the tabular property within the specific row and field has the following format:

form/component:property$field[row]

Example: form/textField1 A binding with this target will write its result to the default property of the textField1 component. If textField1 is a text field, its text property will be changed.

Example: form/image1:imageTable$imageData[0] This binding target changes a binary image in the first row of Image component's Image Table.

Example: form/gauge:datasets[1] This binding target changes the value of a second dataset (with index=1) of a gauge component.

form/script()

This type of binding target is used to launch the widget script named script upon processing the binding, passing the binding evaluation result to the script as its parameter. Bindings with such targets are created automatically upon adding new scripts to the widget template. However, initial properties of such binding does define any script launch conditions. It's necessary to modify these properties to make the script start on widget startup, some event or just periodically.

Example: form/refreshChart() This binding launches the refreshChart widget script that may refresh a chart component to make it displaying the most recent data.

context:action!

This target starts interactive execution of action action from context context. Binding evaluation result is passed to the action as an input value. It should have Data Table type.

Action execution is not available inside widget bindings if the widget is running as a standalone application (outside of Iotellect Client).

Example: cardholders:import! Starts cardholders import action (Cardholders module is a part of Time and Attendance and Access Control solutions), that is an action named import in context with path cardholders.

Widgets, reports, dashboards and several other system objects can be absolute and relative. While an absolute object is launched per se, relative objects are started for a certain context that serves as a data source.

Thus, launching relative widget, report or dashboard via binding target directly won't let the system know what context should it be started for when a binding is executed. Instead, object's launch action located in the target context should be specified in binding target.

Example: Assuming there is a Traffic Chart relative widget that is valid for all network devices. You can open traffic chart of a certain device using binding activator. To do that: Find the source device in the binding target editor Choose Traffic Chart in the action selector

Was this page helpful?

Tell us more

Send

Thank you!