Binding Target

Binding target is an object affected by a binding. For example, it can either be a dashboard component's property or some data within a Iotellect Server context.

In fact, the binding target is a special type of reference.

Several types of binding targets are supported:

• Target with no schema (and thus, no prefix), which points to context data
• Target that uses form schema (and form/ prefix) and points to the dashboard component properties

Dashboard 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 dashboard component.

Dashboard 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.

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.

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.

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 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 dashboard 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!