Skip to main content

Asset Condition Management

Reference Content

ConditionConfirmed behavior
NewDefault for new inventory and requests; becomes Good on first assignment.
GoodCommon operational and default return condition.
RepairGoverned condition recognized by the model; no repair record or work process is attached.
DamagedSet by mark-damaged; may also be supplied on return without automatically changing lifecycle status.
LostSet by mark-lost.

Conditions are canonical enum strings in the domain and database. The HR Operations form shows a narrower UI list that omits Lost; that is a UI distinction, not the domain rule. Registration and detail editing accept a condition string and fall back according to the aggregate operation. Assignment history stores the condition at each lifecycle action.

There is no inspection entity, severity, grading rubric, assessor, photo requirement, maintenance condition workflow, automatic repair routing, or condition-specific allocation rule beyond status transitions. Reports derive damaged/lost signals from status rather than a verified condition report.

Source References

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