Asset UI Limitations
Summary
This page consolidates the verified limitations of the asset UI. Each item is classified as Partial, Not implemented, or Requires confirmation. The overarching theme is that the asset UI is a partial, compatibility-dependent surface built around one HR Operations tab and a read-only self-service view.
Audience
- Developers scoping remediation.
- QA engineers targeting gap verification.
- Support engineers setting customer expectations.
- Solution architects and product owners planning roadmap.
Reference Content
Classified limitations
| Limitation | Classification | Notes |
|---|---|---|
| No dedicated asset detail route/view | Not implemented | No detail screen exists |
| No dedicated assignment screen | Partial | Assignment via Assign To field + approve to Issued only |
| No return control/screen | Not implemented | Return not exposed in UI |
| No damage / lost / retire buttons | Not implemented | Not exposed in UI |
| No in-UI document upload/list/download | Not implemented | No document UI |
| No audit or timeline viewer | Not implemented | No timeline UI |
| No reservation UI | Not implemented | Not present |
| No bulk actions beyond Excel import | Partial | Only Excel import bulk path |
| Full-list loading (no real API pagination) | Partial | Lists load in full; no paging control |
| Frontend visibility is not backend authorization | Requires confirmation | Compat endpoints tenant-scoped, not role-authorized |
| No frontend tests | Not implemented | No unit/component/e2e tests found |
| Accessibility / WCAG conformance | Requires confirmation | No a11y tests or conformance evidence |
| Compatibility-dependent | Partial | UI relies on monolith-shaped compat endpoints (transitional cutover) |
| UI surfaces subset of backend statuses | Partial | Backend has full status/condition set; UI shows a subset |
Status coverage note
The UI references a subset of statuses (Available, Issued, Rejected, Returned) plus condition options (New, Good, Repair, Damaged). The full backend status set (ten) and condition set (five) are documented in the reference material; the UI surfaces only a subset.
Compatibility dependence
The UI depends on monolith-shaped compatibility endpoints and is unaffected by the gateway asset-routing cutover. This dependence is a transitional characteristic rather than a permanent design and is classified as Partial.
Source References
UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsxUI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsxmicroservices/src/asset-service/Api/AssetCompatEndpoints.cs
Related Articles
See Also
Keywords
limitations, gaps, not implemented, partial, requires confirmation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly