Leave Approval Workflow

Summary

Pending Leave can be decided directly or delegated to Workflow Service; the two paths are mutually exclusive for a workflow-managed request.

Audience

Managers, Leave/HR administrators, employees, product owners, QA, and implementers.

Overview

Direct compatibility approval uses authorized employee scope. Extracted-service approval ownership remains Transitional. Approval is only valid from Pending, rechecks active employee/joining date and approved Attendance conflicts, records history/audit, and updates used balance. Multi-step approval is supported only through the configured Workflow definition; the Leave business layer does not define a universal number or sequence of stages. Notification is confirmed on the monolith approval path; extracted-service downstream notification requires confirmation.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveRequest.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Application/WorkflowIntegration.cs
• Controllers/LeaveRequestsController.cs

Related Articles

• Leave overview
• Leave business documentation

See Also

• Attendance module
• Employee module

Keywords

• Leave
• Leave Approval Workflow
• Workforce management

Revision Information

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