Dashboards Overview

Purpose

Developer documentation for dashboard list behavior, dashboard creation flow, page entry behavior, extracted runtime controls, state model, and high-level dashboard composition.

Architecture Summary

• Dashboard developer docs are generated from the extracted dashboard behavior manifest.
• The manifest aggregates flows, forms, dialogs, tables, controls, states, constraints, and widget configuration metadata.
• This scope focuses on how dashboards are listed, created, opened, and structured before widget-specific runtime behavior is considered.

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)

Extracted Tables

• dashboard-list-table — 2 column(s)

Extracted Dialogs

• Widget configuration (widget-config-dialog) — 2 action(s)
• Create Dashboard (dashboard-config-dialog) — 1 action(s)

Extracted Forms

• create-dashboard-form — 2 field(s)

Dashboard List Table

The dashboard list exposes these extracted columns:

• Name
• Created

Dashboard Creation Flow

1. Open the Dashboards area.
2. Click Create Dashboard.
3. Enter the dashboard details.
4. Save the dashboard.

Dashboard Creation Form

The create dashboard form includes these extracted fields:

• Name
• Type

Dashboard Dialog Actions

• Save

Toolbar Runtime Controls

• Add Widget
• Save
• Overview
• Default

Dashboard State Model

The extracted runtime includes these state values:

• Overview
• Default

Behavioral Constraints

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

Developer Notes

• This scope mirrors the user dashboard overview flow, but explains the extracted structure developers need to maintain.
• Use this as the entry document for dashboard list, creation, and page-level architecture.