Effective-Date Resolution
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
The resolver determines what attendance calculation uses for an employee on a date. It combines the local employee profile, active effective assignment, referenced active shift, tenant default attendance policy, and weekly-off rules.
Selection rules
The effective range includes both start and end dates. Open-ended ranges have no upper bound. Batch resolution groups assignments per employee and defensively chooses the candidate with the latest start date. Shift values take precedence, followed by the default policy, then profile fallback values.
Weekly-off rows are cached within the resolver instance. No rows means a Sunday fallback; rows present with none active means no weekly off.
Failure and ambiguity
A missing employee profile prevents resolution. Overlaps should be rejected at creation, but if legacy or concurrent data contains overlaps, latest-start selection masks the ambiguity rather than failing. A stale domain comment suggests assignments are not read, while the resolver demonstrably reads them; executable code is authoritative.
Source References
microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.csmicroservices/src/attendance-service/Domain/Attendance/AttendanceCalculator.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