Weekly-Off Storage
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
Three weekly-off representations coexist.
| Representation | Stored shape | Integrity |
|---|---|---|
| Canonical Attendance rule | Tenant, weekday enum, active state, timestamps | Unique tenant/weekday; tenant filter |
| Leave calendar row | Tenant and day text | Non-unique tenant/day index; tenant filter |
| Legacy row | Optional tenant and day text | Tenant filter; no explicit unique index verified |
Canonical behavior
Weekday is converted to a bounded string. Native updates upsert supplied rules and keep omitted rows. Compatibility replacement activates requested days and deactivates others. Soft state preserves identifiers and history.
Ownership risk
Attendance and Leave persist independent weekly-off data. No database-level relationship or synchronization exists between them. Gateway ownership can change API routing, but it does not merge stored records.
Audit
Canonical changes write audit and timeline evidence. No comparable calendar-specific audit relationship was verified for the Leave and legacy rows.
Source References
microservices/src/attendance-service/Domain/TimeOffice/WeeklyOffRule.csmicroservices/src/attendance-service/Infrastructure/AttendanceDbContext.csmicroservices/src/leave-service/Infrastructure/LeaveDbContext.csModels/WeeklyOff.csData/AppDbContext.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