Asset Request Model
Request lifecycle
A request is an Asset aggregate created directly in Requested, with generated request identity, New condition, requester references, optional due date/notes, Requested history, and AssetRequested event. It is not a separate request entity and is not linked to a specific inventory record.
When workflow integration is disabled, direct issue or rejection remains available. When a workflow instance is attached, direct assign/reject is guarded and the terminal callback owns the decision. Approval immediately issues to the original requester. Duplicate callbacks are acknowledged when the record is no longer Requested.
There is no reservation, inventory matching, request-to-stock link, quantity, eligibility policy, approver entity, request amendment, cancellation, or waitlist.
Requires confirmation
Production ownership, authorization governance, operational policy, and future architecture require confirmation where the source does not enforce them.
Source References
microservices/src/asset-service/Domain/Asset/Asset.csmicroservices/src/asset-service/Application/Commands/AssetCommands.csmicroservices/src/asset-service/Application/WorkflowIntegration.cs