Compatibility
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
A legacy-shaped adapter allows existing clients to use Attendance Service without changing their shift and weekly-off payloads. Gateway-controlled ownership selects the canonical service or existing owner independently from broader attendance cutover.
Preserved behavior
The adapter exposes bare legacy response bodies, compatibility identities, legacy status behavior, textual overtime-rule translation, and full-set weekly-off replacement. Administrative mutation checks mimic the monolith.
Intentional differences
Canonical deletion is soft. Compatibility delete deactivates the shift and active assignments, whereas the direct command blocks deletion when assignments are active. The monolith previously removed the shift record and cleared employee references. Direct weekly-off updates are partial upserts; compatibility replacement is complete.
Cutover posture
The repository contains parity, smoke, and go/no-go automation, but retirement criteria, duration of dual ownership, write-freeze expectations, reconciliation ownership, and rollback decision authority are not encoded in application code.
Source References
microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.csmicroservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.csmicroservices/src/gateway-api/Program.csServices/ShiftService.csServices/WeeklyOffService.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