Skip to main content

Holiday 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​

Holiday persistence is Not implemented in the canonical Attendance shift-policy model. It exists in Leave Service and the monolith.

Leave-owned holiday​

The Leave entity stores tenant, name, date, and type. Name and type are required and length-bounded. A non-unique tenant/date index supports lookup, and a tenant query filter applies. It has no relationship to Shift or EmployeeShiftAssignment.

Legacy holiday​

The monolith stores equivalent display, date, type, and optional tenant fields. A tenant query filter applies. No explicit holiday index or uniqueness constraint was found in monolith fluent mapping.

Scheduling boundary​

Effective shift resolution checks canonical weekly-off rules but does not join Leave holidays. Holiday-aware leave and payroll workflows query their own calendar boundary. Authoritative holiday ownership and synchronization require confirmation.

Source References​

  • microservices/src/leave-service/Domain/Leave/CalendarEntities.cs
  • microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
  • Models/Holiday.cs
  • Data/AppDbContext.cs

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