Expense Workflow Events
Summary
Expense workflow integration is HTTP-based. Workflow initiation, optional state verification, and the terminal callback are not integration events.
Confirmed workflow boundary
A callback resolves the claim by claim identity or workflow instance identity. Unsupported decisions and mismatched subject types are rejected. If the claim is already terminal, the callback is recorded as ignored and acknowledged without another domain event. Optional live-state verification can reject a callback whose decision conflicts with the retrieved terminal state.
Expense exposes a stable callback endpoint, but no broker subscription consumes a workflow event.
Not implemented
- WorkflowStartedEvent from Expense
- WorkflowCompleted subscription in Expense
- Workflow callback replay queue
- Event-based workflow state synchronization
Requires confirmation
Callback authentication ownership, replay operations, terminal-state reconciliation, workflow availability objectives, and future event-based workflow integration require confirmation.
Source References
microservices/src/expense-service/Application/Commands/ExpenseClaimCommands.csmicroservices/src/expense-service/Application/WorkflowIntegration.csmicroservices/src/expense-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/expense-service/Api/ExpenseEndpoints.cs
Related Articles
See Also
Keywords
- Expense events
- Workflow Events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly