Asset Management Known Limitations

Reference Content

Asset categories/hierarchy, governed type catalog, reservation, and stock quantity management.
Employee-to-employee, location, or department transfer.
Maintenance requests, schedules, work orders, service providers, repair dates/costs, and return-to-service controls. Repair is only a recognized status/condition and clearance blocker.
Warranty dates, providers, claims, expiry alerts, and service linkage.
Vendor, purchase, invoice/order, currency, cost, depreciation, procurement, payroll, and finance records or integrations.
Location/department ownership; theft-specific incidents; recovery/replacement; disposal/archival; acknowledgement/signature; legal or financial liability.
Return-due reminders and overdue processing.

Dedicated Asset Service coexists with compatibility routes and shared HR Operations UI.
Type governance is free text; UI type/condition lists are not canonical.
Employee integration stores identifiers without existence, active-status, or ownership verification.
Workflow approval is optional; manual and workflow-managed request paths coexist.
Dashboard metrics are client-derived from status text and are not date-filtered server reports.
Inventory list is capped at 1,000 without pagination, search, total count, or configurable sorting.
Import/export is surfaced in shared UI without a verified domain-level bulk contract.
Repair has no native transition command or operational process.

Asset endpoints configure authentication middleware but do not require endpoint authorization or fine-grained policies.
Asset code uniqueness is application-enforced rather than a tenant+code database uniqueness constraint; serial uniqueness is absent.
Audit, timeline, documents, and stored content have no documented retention, legal hold, redaction, or access-governance policy.
Document reference removal retains stored content; lifecycle and ownership of that content require confirmation.
No dedicated source-backed Asset Service automated test project was identified in the reviewed module tree; smoke/backfill verification does not replace business acceptance testing.