Dashboards & live views
Turn the data you can access into a useful dashboard without building another app.
dashboard widgets metrics charts composition reportingOn this page
Make a dashboard useful to youWhere the data comes fromMetrics, tables, and custom viewsRefine and restore the layoutMake a dashboard useful to you
Ask your agent to arrange the dashboard in the Dashboard app around the information you check regularly. It can inspect the current layout, add or update supported widgets, and adjust their configuration. You do not need to build an app just to show a metric, a list, or a table. To land on it when you open Opser, pick it as your home page.
Example widgets show 12 open requests and 3 needing review. REQ-104 from Acme Studio is in progress; REQ-105 from Juniper Labs is pending.
Add a compact view of the open requests I can access, grouped by status. Put the total above a table of the oldest requests. Keep my existing widgets.
Name the source and the question the view should answer. The agent should check what data is available before choosing a widget.
The agent's dashboard tools come with the Dashboard app, so they are there only when the app is installed and you can open it. Earlier versions of the app do not include them: when the Dashboard app shows Update available, someone who manages apps can install the new version with Update app. See Managing apps.
Where the data comes from
A widget can show any business data you can read: your own datasets and the tables of the apps you can open. The Dashboard app reads them the way the agent's data tool does, read-only, so a dashboard never shows an app you cannot open and never changes a record.
When an app offers a read operation for composition, the agent prefers it: the operation keeps the app's own logic and keeps working when the app changes its tables. Otherwise the widget queries the tables directly, and the agent runs the query before saving the widget. See How apps work together.
Metrics, tables, and custom views
The agent can build read-only metrics, charts, tables, lists, and supported custom views. Give it the grouping, date range, units, and empty-state behavior you expect.
A useful view shows its meaning clearly: distinguish a count from a currency value, keep the date range visible, and verify the result against the source. Custom views use supported display components rather than an unrestricted web application.
Refine and restore the layout
Ask for a focused change to the current layout. The dashboard keeps revision history so an earlier layout can be restored as a new revision. Restoring a layout does not roll back the underlying business data.
Check the populated dashboard after a change, including narrow screens and empty results. Refresh behavior depends on the widget configuration; a view is not necessarily updated at the exact instant a source record changes.