Dashboard Realtime

Purpose

Developer documentation for runtime state handling, toolbar controls, historical versus live behavior, and realtime dashboard considerations.

Runtime Model

Dashboard runtime behavior is shaped by selected state, active entity context, toolbar selections, and widget-level data requirements.
Runtime controls influence whether widgets resolve live data, historical data, or context-specific data.
Dashboard behavior can vary between realtime and historical modes depending on widget implementation and selected context.

Extracted Structure Summary

Extracted flows: 4
Extracted controls: 5
Extracted dialogs: 2
Extracted forms: 1
Extracted tables: 1
Extracted state groups: 1
Extracted widget config entries: 62

Extracted Flows

Add widget (add-widget-flow) — 3 step(s)
Create dashboard (create-dashboard-flow) — 4 step(s)
Save dashboard changes (save-dashboard-flow) — 2 step(s)
Switch dashboard state (switch-dashboard-state-flow) — 2 step(s)

Add Widget
Save
Overview
Default

Dashboard States

Overview
Default

Runtime Constraints and Notes

Dashboard changes require an explicit save action when editing is available.

Historical and Live Data Considerations

Realtime mode should explain how widgets extend, refresh, or merge live values into runtime state.
Historical mode should explain how selected time windows influence widget queries and rendering.
Runtime entity selection should explain how widgets resolve aliases, entity-bound keys, and active context.
Live update handling should explain how incoming telemetry affects dashboard state and widget rendering.

Developer Notes

This scope mirrors the user dashboard page runtime coverage, but explains the technical runtime model developers maintain.
Widget field definitions and per-widget defaults belong in the dashboard widgets scope.