There are several ways to open a dashboard:
| • | Using the Open Dashboard action of a Dashboard Context. This method should be used for absolute dashboards. For relative dashboards, this method will open the dashboard for the AggreGate Server root context, causing wrong behaviour in most cases. |
| • | Using an Open Dashboard action (see below) to start a relative dashboard for a certain Device or system resource. |
This action may be found in every context for those relative dashboard's validity expression is true. When the Open Dashboard action is started in some context, this context becomes a default context for the opening dashboard. For example, if a User Overview dashboard is created for a User context (e.g. has Validity Expression {.#type} == 'user'), an action called User Overview will appear in the context of every AggreGate Server user. Its description is the same as that of the dashboard itself. Actions that are used to open dashboards may be easily recognized by a 
icon.
Here is what an Open Dashboard action looks like in a context menu within AggreGate Client:
For this action to be available, the user must have an effective permission level of Observer in two contexts:
| • | Dashboard context of the actual dashboard being launched |
| • | The context on which the dashboard operates, i.e. the one where Launch Action is defined |
Dashboard Window
The dashboard is opened in a separate tabbed window in any AggreGate Server User Interface. When dashboard window is closed, all dashboards components are stopped (e.g. if it were running widgets) and hidden.
Here is how a dashboard look like in AggreGate Client:
