The AggreGate interface is rich in functionality, and the context tree can get quite deep and complex. To make navigation easier, Favourites have been implemented.
Favourites allow AggreGate users to execute commonly-used actions with a single mouse click. You don't have to "dig" in the context tree -- you can have instant access to whatever you use the most via the Favourites, which work like "shortcuts" or "quick links" leading to various contexts. The Favourites are easy to locate in all AggreGate user interfaces. For example, this is what they look like in AggreGate Client:
The following columns are displayed in the table:
Number: This is the line number of the favourite in the table.
Description: This is a textual description of the action which will be executed (can be changed by the user).
Server: This is the server on which the favourite is configured.
Context Mask: This is the context mask to which the favourite applies or description of the context, if the mask resolves to a single context (i.e, does not contain any wildcards).
Action: This is the description of the Action which will be executed on the context mask when the favourite is launched.
Every line in the table functions as a link. When the line is clicked, the Favourite is launched. You can click any column.
In the AggreGate Client, when a workspace contains several server connections, the resulting favourites table includes all favorites that are available under all accounts. In effect, the favourites are collected from all AggreGate Server connections and displayed in one unified table in the AggreGate Client. This lets you use just one Favourites table to navigate all over your "AggreGate Universe".
Unlike actions launched "directly" (e.g. from the System Tree of AggreGate Client), actions started using Favourites facility may use custom execution parameters.
|
Every user has his own set of Favourites. |
|
Related tutorial: Performing an Action With Multiple Devices |
Administering Favourites
Two contexts are used to administer the automatically started actions: One is the general Favourites context, which serves as a container. The other is the Favourite context, which holds the information for one particular favourite item. |
|
Launching Widgets, Reports and Dashboards via Favourites
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 over a certain context that serves as a data source.
Thus, adding relative object's launch action to favourites directly won't let the system know what context should it be started for when a favourite is clicked. Instead, object's launch action located in a target context should be added to favourites.
|
Example: Assuming there is a Traffic Chart relative widget that is valid for all network devices. You can add traffic chart of a certain device to favourites. To do that:
|
