Leave Future Evolution

Summary

Only directions already evidenced by foundations, optional integrations, gateway cutover, and validation tooling are listed.

Audience

Architects, technical/product owners, developers, QA, and DevOps.

Overview

Source-evidenced directions are completion of carry-forward and encashment foundations, optional Workflow-managed approval, continued Employee projection integration, gateway direct/shadow/cutover validation, and downstream event-driven Payroll/Notification ownership.

The following require confirmation before design or commitment: centralized policy assignment/effective dates, complete policy enforcement, balance reservation/accrual processing, request edit/resubmit, unified Leave/Attendance calendar ownership, final authorization model, dependency readiness probes, business metrics, caching/pagination, reconciliation tooling, broader notification coverage, and comprehensive automated test suites.

No delivery date, migration promise, final target architecture, or operational procedure is implied.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveExtras.cs
• microservices/src/leave-service/Application/WorkflowIntegration.cs
• microservices/src/gateway-api/Program.cs
• microservices/scripts/smoke-leave.ps1

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Future Evolution
• Technical architecture

Revision Information

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