Dashboard Live

AgrEGG provides a dashboard editing area that is separate from the standard dashboard configuration workflow. In the codebase this feature is exposed as Dashboard Live.

The purpose of Dashboard Live is to let authorized users assemble, save, refine, and publish dashboard compositions in a more iterative way than the classic static dashboard generator.

When to use it

Dashboard Live is useful when users need to:

  • build a dashboard composition interactively;

  • save a draft before publishing it for broader use;

  • clone an existing live dashboard and adapt it;

  • preview or embed a dashboard in a lightweight form;

  • work on temporary dashboard structures without immediately replacing an existing dashboard.

Main concepts

The feature distinguishes between a working dashboard and a published result.

Important concepts visible in the code are:

  • a live dashboard can exist as a draft;

  • a dashboard can be temporary;

  • saved live dashboards can be listed and reopened later;

  • a saved dashboard can be cloned;

  • a live dashboard can be published or converted into a normal dashboard structure;

  • an iframe-oriented rendering path is available for embedding scenarios.

Typical workflow

The expected workflow is:

  • open the Dashboard Live editor from the relevant Business Unit context;

  • choose graphs, reports, tabular reports, and filters;

  • save the current composition as a draft;

  • reopen and refine the draft if needed;

  • clone it when a similar dashboard is needed for another use case;

  • publish the result when the draft is ready to become available as a standard dashboard.

Content that can be included

The Dashboard Live area is designed to work with dashboard-oriented objects already present in the platform, such as:

  • graph types;

  • KPIs;

  • reports;

  • tabular reports;

  • filters and drill-down settings;

  • dashboard menu metadata.

Depending on permissions and configuration, not all users will see the same set of editable objects.

Publishing and lifecycle

Saving a live dashboard is not necessarily the same as publishing it.

In general:

  • saving stores the current draft state;

  • publishing promotes that state into a more stable dashboard definition;

  • deleting a live dashboard can also remove dependent temporary objects created for that dashboard;

  • temporary dashboards are intended for intermediate work rather than long-term navigation structures.

Permissions

Dashboard Live is role-based. The code indicates that access, editing, and publishing are restricted to authorized users.

Users may therefore encounter one of these situations:

  • they can view and edit live dashboards;

  • they can open only the dashboards they created or are allowed to access;

  • they can see the feature but not publish;

  • they receive an authorization error when trying to access a dashboard created by someone else.