Workflow Integration

Summary

Optional Workflow starts for persisted Pending claims, links an instance, suppresses direct decisions, and applies idempotent terminal callbacks. Expense does not own Workflow internals. Trust, authorization, and operational failure governance require confirmation.

Audience

Backend and frontend developers, QA, architects, DevOps, support, and new engineers.

Source References

• microservices/src/expense-service/Application/WorkflowIntegration.cs

Related Articles

• Technical overview
• Business documentation

See Also

• Expense module

Keywords

• Expense technical
• Application/WorkflowIntegration.cs

Revision Information

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