Leave Workflow Integration
Summary
Workflow delegation is optional and changes who owns a Pending Leave decision.
Audience
Leave/Workflow developers, architects, QA, support, and product engineers.
Overview
When enabled, administrative auto-approval is suppressed, a workflow instance is started, and its identity is attached to the Pending request. Direct approve/reject is refused while the request remains workflow-managed. Completion maps approved/completed or rejected outcomes; duplicate callbacks on terminal Leave are acknowledged without reapplying balance effects.
Start and verification failures have environment-sensitive application handling, whose non-production details are intentionally excluded. Workflow owns task sequencing and assignees; Leave owns its request state and balance effect. This integration is Transitional and not a universal approval hierarchy.
Source References
microservices/src/leave-service/Application/WorkflowIntegration.csmicroservices/src/leave-service/Application/LeaveWorkflows.csmicroservices/src/leave-service/Infrastructure/WorkflowServiceClient.cs
Related Articles
See Also
Keywords
- Leave Service
- Leave Workflow Integration
- Technical architecture
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly