Dashboard

Purpose

The Dashboard provides a consolidated view of your project's health and the most important cards (widgets). Cards are visual summaries of quality and performance indicators — they show totals, counts, and small trend summaries.

Key areas

• Top bar: date range, iTwin / iModel selector and changeset selector.
• Cards area: a grid of cards (donut, stat, bar, table, etc.) showing high-level metrics.
• Trends: compact trend indicators and links to saved snapshots.

Cards

Each card on the dashboard has various presentation options

• Categories : Represents the cards title

• Good / Bad chip : represents if the results are in the good or bad range

• Settings : Enables the user configuration of any parameters for the card

• 42 the number of groups for the underlying ecSQL

• 156874 the number of elements associated with the 42 groups

• 38 good groups, those groups which pass the defined rules

• 63050 the number of elements that are part of the good group

• 4 bad groups, those groups which fail the defined rules

• 93824 the number of elements that part of the bad groups

• 40% the quality score ie 63050/154687 to provide the quality score

• Trends : If Trends are enabled, then this will show the trends between user determined saves. If the user does not Save the dashboard score then there will be no trends

• : imodelconsole will open the imodelconsole with the underlying query and expanded parameters.

Looks like the Save option is not enabled on Dashboards

Notes

• Cards are defined by a CardDefinition which includes a presentation type and an ECSQL query. The evaluation rules (thresholds or ratio) are part of the card definition and determine the good/warning/bad classification shown on the card.
• Cards on the dashboard cannot currently be edited as they are part of an investigation into utilising a common semantic model. This will probably not be extendable by users and may be discontinued in preference for the Quality tab style cards