Weekly Off Storage

Summary

Each weekly-off row represents one tenant and one day of the week, with active state and audit timestamps.

Audience

• Backend developers, Time Office implementers, QA engineers, and support engineers

Reference Content

Confirmed storage behavior

Day of week is persisted as a required string conversion. A unique tenant/day index prevents duplicate rules for the same tenant and day. Repository reads order rules by day and business evaluation considers active rows.

Weekly-off rules have tenant scope but no employee, shift, Attendance policy, recurrence-week, or holiday foreign key. Scope is therefore tenant-wide in the current model. Deletion is represented by active-state changes in domain behavior; no cascade relationship is configured.

Holiday, Leave, and weekly-off precedence is Requires confirmation and is not implied by this schema.

Source References

• microservices/src/attendance-service/Domain/TimeOffice/WeeklyOffRule.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/attendance-service/Infrastructure/Persistence.cs

Related Articles

• Attendance database
• Attendance technical documentation
• Attendance API documentation

See Also

• Attendance business documentation
• Attendance overview

Keywords

• Attendance persistence
• EF Core
• PostgreSQL

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly