Asset Workflow Integration
HTTP workflow boundary
IWorkflowClient defines start and state-read operations. A null implementation is injected when disabled; a typed HTTP client is registered when enabled. The real adapter forwards tenant, actor, role, and correlation context and logs remote failures without exposing them as unhandled transport exceptions.
AssetCommands persists the request before remote start. Successful start stores the instance and evidence. Workflow-managed requests block direct assign/reject. Callback resolution supports subject or instance association, normalizes terminal decisions, is idempotent after the request leaves Requested, and can compare the callback with live workflow state.
No callback authentication policy, distributed transaction, compensating delete, inbound event consumer, workflow-definition validation at startup, or Asset Service ownership of approver policy exists.
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/Application/WorkflowIntegration.csmicroservices/src/asset-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/asset-service/Application/Commands/AssetCommands.cs