The Auto Run feature allows actions to be executed automatically when a user logs into a AggreGate Server User Interface, such as AggreGate Client. Auto Run actions are very useful for creating "dashboards", which are sets of widgets, queries, and reports which are automatically displayed in pre-set positions as soon as a user launches AggreGate Client. Another use would be to automatically display the status of a particular mission critical Device.
Actions are launched in the same order as they appear under the Auto Run context. Children of this context may be reordered. AggreGate Client users may use reordering feature of the System Tree for that, while other AggreGate Server User Interfaces provide similar facilities.
Unlike actions launched "directly" (e.g. from the System Tree of AggreGate Client), actions started using Auto-Run facility may use custom execution parameters.
|
Every user has his own set of Auto Run Actions. |
|
Related tutorial: Creating a Dashboard to Monitor Your Devices in Real-Time |
Administering Auto Run
Two contexts are used to administer the automatically started actions: One is the general Auto Run context, which serves as a container. The other is the Auto Run Action context, which holds the information for one auto-started action. |
|
Launching Widgets, Reports and Dashboards via Auto Run
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 auto run directly won't let the system know what context should it be started for. Instead, object's launch action located in the target context should be added to auto run.
|
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 auto run. To do that:
|
