Compatibility Persistence
Audience
Developers, database engineers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified Workforce Scheduling persistence behavior and boundaries.
Summary
Compatibility persistence preserves legacy shift identity in a separate canonical compatibility field and transforms legacy employee shift references into effective-dated assignments.
Backfill behavior
The specialized context disables store generation for compatibility identity. Shift data is validated and normalized before insertion/update. Weekly-off text is parsed into canonical weekday values. Employee references are mapped only when their shift compatibility identity resolves.
The backfill supports dry-run, resume, validation-only, scoped tenant, batching, and optional assignment omission in source code. Operational invocation details are intentionally excluded.
Compatibility writes
The compatibility service writes canonical entities, not a duplicate compatibility database. Delete deactivates the canonical shift and active assignments. Weekly-off replacement changes active flags while retaining canonical rows.
Failure boundaries
Shift, weekly-off, assignment, and completion-audit saves are separate. Unmappable or invalid source data is reported rather than guessed. Cross-step atomicity was not verified.
Source References
microservices/src/attendance-service/Backfill/ShiftPolicyBackfillTypes.csmicroservices/src/attendance-service/Backfill/ShiftBackfill.csmicroservices/src/attendance-service/Backfill/WeeklyOffBackfill.csmicroservices/src/attendance-service/Backfill/ShiftAssignmentBackfill.csmicroservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.cs
Related Articles
See Also
Keywords
- Workforce Scheduling database
- Shift persistence
- Attendance policy storage
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20