Dashboards
Orientation is in Getting started.
OpCon Continuum opens on a dashboard tailored to the user. The platform routes each user to the dashboard that matches their role (remembering their last-viewed choice), so the first thing they see is relevant to what they do.
The three dashboards
| Dashboard | For | Typical widgets |
|---|---|---|
| Administrator | Keeping the environment healthy | Environment health, agents, relays, agent-pool utilization |
| Operator | Watching the daily run | Failed jobs, event summary, workflow/job status counts, agent-pool job queue |
| Business | Non-technical users | Self-service catalog, the user's events |
The Business dashboard's My Events widget shows your own events — the requests and actions recorded against your signed-in identity, scoped to the environment the dashboard is showing. Earlier builds showed the same five sample events, attributed to the same name, to everyone; that's fixed. The widget requires a signed-in identity, so it reports an error rather than falling back to everyone's events if it can't tell who is asking.
The Administrator dashboard's Agents widget counts agents by the status you would read off an agent list, which combines observed connectivity with any operator mark. An agent marked out of service is counted as Marked Offline or Marked Draining rather than as Online, and selecting that slice lists exactly those agents. Agent-pool utilization follows the same rule: a pool's online figure counts only the agents that can actually take work.
- The dashboards are read-only summaries — they surface state from other areas (Processes, Agents, Events, Self Service); they don't change anything.
- Which dashboard a user lands on follows their role/last choice, so two users may see different home screens — that's expected.
- My Events is per-user, so two people looking at the same dashboard see different lists. An empty list means you haven't raised anything, not that the widget is broken.
- The widgets update by themselves, over a live connection the browser holds open. It is reconnected automatically as your session refreshes its credentials. Earlier builds kept the original connection open past that point, and the widgets quietly stopped updating — for up to an hour on a dashboard left open — while still showing figures that looked current. Reloading the page was the only way to notice. That is fixed; if a dashboard does look stale now, reloading is still the quickest check.
- The Updated time shows when the widgets last changed. It is set each time live data arrives and each time you select Refresh all widgets. There is no other warning when updates stop, so if the time stops moving on a dashboard you are watching, select Refresh all widgets or reload the page. While Pause auto-refresh is on, the widgets do not update until you resume.
Related topics