Domain Model
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
Four tenant-owned concepts form the shift-policy foundation:
| Concept | Purpose | Lifecycle |
|---|---|---|
| Shift | Named daily working window and calculation thresholds | Create, update, activate, deactivate |
| Employee shift assignment | Effective-dated link from an employee record to a shift | Create, end, deactivate |
| Weekly-off rule | Tenant calendar day state | Create, activate, deactivate |
| Attendance policy | Default calculation thresholds and ordered status rules | Create, update, activate state |
Aggregate boundaries
Assignments reference shifts and employees by identifiers without navigation properties. Policies own rule collections. Shifts calculate their scheduled duration, including windows that cross midnight. Soft activation state is the normal lifecycle for canonical configuration.
Domain events
These aggregates inherit domain-event support, but no scheduling-specific event mapping was verified in the persistence outbox translator. Attendance lifecycle events are mapped; shift-policy changes are represented through audit and timeline records instead.
Missing model
No schedule period, roster, team, rotation, availability, swap, demand forecast, or publication aggregate was found.
Source References
microservices/src/attendance-service/Domain/TimeOffice/Shift.csmicroservices/src/attendance-service/Domain/TimeOffice/EmployeeShiftAssignment.csmicroservices/src/attendance-service/Domain/TimeOffice/WeeklyOffRule.csmicroservices/src/attendance-service/Domain/TimeOffice/AttendancePolicy.cs
Related Articles
See Also
Keywords
- Workforce scheduling
- Shift policy
- Attendance integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20