Skip to main content

Asset Management

Summary​

Asset Management records tenant-owned inventory, employee requests and custody, returns, availability, damage or loss, retirement, supporting documents, and lifecycle evidence. The implementation is Transitional: the dedicated service is source-backed, while compatibility routes and the existing HR Operations UI still shape part of the experience.

Audience​

Business owners, HR and asset administrators, employees, implementation teams, engineering, QA, support, and architecture.

Overview​

  • Business documentation describes verified behavior and limitations.
  • Technical documentation describes the implemented service architecture, domain, application, persistence, integrations, security context, observability, compatibility, and testing evidence.
  • API documentation inventories the implemented native, compatibility, workflow, document, diagnostics, and host HTTP surfaces, including models, validation, security behavior, errors, discovery, testing evidence, and limitations.
  • Database documentation describes the implemented EF Core persistence model: the AssetDbContext, persisted object sets, aggregate and child storage, tenant filters, keys and indexes, value-object conversions, transactions, migrations, development seeding, the transitional backfill, and persistence limitations.
  • Events documentation describes the implemented event model: six domain events mapped 1:1 to six shared integration contracts, transactional outbox staging, the hosted relay, the confirmed Notification consumer, the HTTP workflow/document/gateway boundaries, identifier-only employee references, compatibility identity in the payload, and reliability limitations.
  • UI documentation describes the verified frontend: the HR Operations asset tab and employee self-service views, routes and navigation, the asset form, requests and approvals, compatibility UI, validation, permissions and visibility, and UI limitations.
  • Operations documentation describes the service runtime: startup and middleware, configuration boundaries, health and diagnostics, logging and correlation, audit/timeline/outbox/workflow/document/notification/gateway operations, migration and backfill boundaries, smoke testing, recovery, monitoring, checklist, escalation, and limitations.
  • Troubleshooting documentation provides non-destructive diagnostics across authentication, tenant context, the asset lifecycle, workflow callbacks, documents, notifications, the outbox, the gateway and compatibility slice, and migrations, with a diagnostic decision tree.
  • Reference documentation consolidates terminology, the status/transition catalog, routes, an API summary, a permissions matrix, a validation catalog, an event summary, an integration matrix, a database summary, the implementation-maturity matrix, consolidated limitations, and the module source map.

The older /modules/asset documentation URL remains separate and unchanged.

Requires confirmation​

Production ownership, policy governance, fine-grained authorization, retention, and the roadmap for capabilities classified as not implemented require confirmation.

Source References​

  • microservices/src/asset-service/Domain/Asset/Asset.cs
  • microservices/src/asset-service/Program.cs
  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx

See Also​

Keywords​

  • Asset inventory
  • Employee custody
  • Asset lifecycle

Revision Information​

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