Dashboards subdivide in two types:
| • | Absolute |
| • | Relative |
Absolute Dashboards
Absolute dashboards are most used to display data coming from multiple different sources, e.g. several devices.
In some cases, an absolute dashboard may display or control a pre-defined device or resource those name is hard-coded into dashboard elements' parameters.
Absolute dashboards are opened by right-clicking on a dashboard context (
) and selecting open dashboard action.
Relative Dashboards
Relative dashboards show status of a single device/resource that is not hard-coded into dashboard's configuration. A relative dashboard is opened for a certain device/resource by right-clicking on it and selecting launch dashboard action those name match dashboard description (this action's icon is always ).
Relative dashboards have a so-called validity expression. It helps AggreGate Server determine what contexts the dashboard can work with. It is written using the built-in Expression Language. When a new dashboard is created, or the validity expression itself is updated, AggreGate Server evaluates this expression for every context in the system. If the expression evaluates to true, the server considers that the dashboard "understands" the data of this context and installs a Open Dashboard action into it.
|
Example: The Validity Expression is often used to check the type of context. This is very useful for creating dashboards that work with certain types of Devices or system resources. For example, to make a dashboard work with every Modbus device in the system, set the Validity Expression to {.#type} == 'device.modbus'. This expression will resolve to TRUE when the type property for the context being checked (indicated by "." relative context path) equals device.modbus. |
Validity Expression Resolution Environment: |
|
Context for that validity is verified. |
|
None. |
|
0 |
|
Standard variables only. |
|