Skip to main content

Effective-Date Storage and Resolution

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​

Effective-date behavior is represented by assignment start, optional inclusive end, and active state. Resolution combines stored employee profile fallback, effective assignment, active shift, default policy, and weekly-off rules.

Stored range​

Start is required and normalized to a date. End is nullable. The range includes both boundaries. Active state gates lookup independently from dates.

Query behavior​

Single resolution obtains the employee profile and relevant assignment/shift. Batch resolution preloads profiles, assignments, and shifts, groups by employee, and chooses the latest-start candidate defensively.

Integrity gap​

Overlap prevention is application-side. If overlapping rows exist, latest-start resolution selects one rather than reporting corrupt data. No temporal constraint or history table was verified.

Source References​

  • microservices/src/attendance-service/Domain/TimeOffice/EmployeeShiftAssignment.cs
  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Infrastructure/Persistence.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