Dashboard cards
Dashboard cards turn scope data, saved queries, tasks, reports, and static content into focused views and actions.
Cards are arranged on a dashboard grid and each card stores its own configuration under cardConfig.data.
This catalog documents the cards registered by Neops Web Client v5.0.0 against @zebbra/ngx-neops-app-components 5.2.0.
The incorrect-dashboard-type placeholder is intentionally excluded because users cannot select it as a card.
Catalog
| Card | cardId |
Documentation |
|---|---|---|
| Markdown | markdown |
Available |
| Status | status |
Available |
| Query box | query |
Available |
| Bar chart | bar-chart |
Available |
| Dynamic map | map-dynamic |
Available |
| Table | table |
Available |
| Task selector | task-selector |
Available |
| Task execute | task-execute |
Available |
| Static map | map |
Available |
| Pie chart | pie-chart |
Available |
| Status Overview | status-overview |
Available |
| Network topology diagram | network-diagram-topology |
Available |
| Predefined Searches | predefined-query-selector |
Available |
| Query with predefined filters | query-with-predefined-filters |
Available |
| Report execute | report-execute |
Available |
| Report selector | report-selector |
Available |
| Aggregation pie chart | aggregation-pie-chart |
Available |
| Static data table | static-data-table |
Available |
Reading a card page
Each page uses the same order: purpose, live example, requirements, complete field reference, copyable configurations, runtime behavior, and limitations. Requiredness and defaults describe actual editor and runtime behavior, not only TypeScript types.
Interactive examples use a static Card Lab that mounts the production SDK component and guided configuration form against deterministic demo data. The first Card Lab release covers Markdown and Status without starting a Neops backend or authentication flow. Cards that depend on backend discovery, execution, topology, or external map tiles say so explicitly instead of substituting a fake interactive control.
The catalog inventory and source fingerprints are recorded in card-contracts.json.
The documentation workflow regenerates that manifest from the exact installed SDK tag and reviews any page reported as missing, version-mismatched, or source-changed.
