Leave Integration
Audience
Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified technical behavior and boundaries for the workforce-scheduling capability.
Summary
No direct shift-assignment integration was verified in Leave Service. Leave workflows evaluate leave conflicts, holidays, and weekly offs through leave-owned abstractions, while Attendance Service resolves shift assignments for attendance calculation.
Boundary
This means an employee's effective shift does not directly alter leave duration, eligibility, or approval in the reviewed code. The similarly named weekly-off concepts belong to different service boundaries during the transition and can be routed through compatibility behavior at the edge.
Risk
Without an explicit synchronization contract, weekly-off configuration can diverge across owners. No scheduling event consumer, shift-aware leave calculation, or automatic leave recalculation was found.
Requires confirmation
The authoritative weekly-off owner after cutover, expected synchronization, and whether leave should become shift-aware are product and architecture decisions, not verified implementation behavior.
Source References
microservices/src/leave-service/Application/LeaveWorkflows.csmicroservices/src/attendance-service/Application/Services/AttendancePolicyResolver.csmicroservices/src/attendance-service/Domain/TimeOffice/WeeklyOffRule.cs
Related Articles
See Also
Keywords
- Workforce scheduling
- Shift policy
- Attendance integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20