Skip to main content

Holiday and Weekly-Off Integration

Audience

Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content

This page records source-verified technical behavior and boundaries for the workforce-scheduling capability.

Summary

Attendance Service stores tenant-scoped weekly-off day rules. The effective-policy resolver uses them to label dates during attendance processing. No holiday aggregate exists in this scheduling slice; holidays are handled outside the slice.

Weekly-off semantics

  • When no weekly-off rows exist, Sunday is the fallback.
  • When rows exist but every row is inactive, there is intentionally no weekly off.
  • Direct updates upsert supplied days and leave omitted rows unchanged.
  • Compatibility updates replace the complete active day set and can clear it.

Holiday boundary

Leave workflows own holiday-aware leave decisions. No verified scheduling resolver merges a holiday calendar with the effective shift. Attendance holiday treatment therefore depends on attendance workflows outside the shift assignment itself.

Transitional risk

Compatibility routing can move the legacy weekly-off surface to Attendance Service independently of broader attendance ownership. The retirement plan and single authoritative owner require confirmation.

Source References

  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Domain/TimeOffice/WeeklyOffRule.cs
  • microservices/src/leave-service/Application/LeaveWorkflows.cs

See Also

Keywords

  • Workforce scheduling
  • Shift policy
  • Attendance integration

Revision Information

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20