Skip to main content

Asset Dashboard and Metrics

Summary

The asset UI surfaces a single "Assets" metric card whose value is a client-side count of the loaded list, not a server-side aggregate. There is no dedicated server-side asset reporting in the UI; all displayed metrics are frontend-derived from the loaded workspace data.

Audience

  • Developers reasoning about metric derivation.
  • QA engineers validating the metric card and loading states.
  • Support engineers explaining metric values to customers.
  • Solution architects and product owners assessing reporting gaps.

Reference Content

The "Assets" metric card

Within the admin asset tab of HrOperationsPage, a metric card labelled "Assets" displays data.assets.length. This is the count of the currently loaded asset list in the browser, computed client-side. It is not a server aggregate and does not reflect server-side totals beyond what has been loaded into the workspace.

Workspace data source

The workspace list loads via an API GET that reads res.data.assets || res.data.Assets. The same loaded collection drives both the table and the metric count. The ESS dashboard additionally shows an "Assigned assets" section (documented under Employee Self-Service).

Loading and empty states

The list is loaded in full into the workspace. When no assets are present, the surface shows an empty state ("No assets" / "No asset requests or assignments found."). There is no client-side pagination control tied to real API paging.

No server-side asset reporting in the UI

The UI does not present server-side asset reporting, dashboards, or aggregates beyond the client-derived count. Any richer reporting is out of scope of the current frontend and is classified as not implemented in the UI.

Data flow

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/dashboard/DashboardPages.tsx

See Also

Keywords

asset metric card, workspace, client-side count, empty state, no server reporting

Revision Information

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly