Effective-Date Behavior

Summary

This page records verified Workforce Scheduling UI and operational behavior and identifies unsupported capabilities explicitly.

Audience

Business users, developers, QA engineers, support engineers, solution architects, and implementation partners.

Reference Content

Effective ranges use inclusive start and end dates; a missing end date is open-ended. Creation rejects an end date earlier than its start and rejects overlap with any active assignment for the same worker. When no start is supplied, the command uses the current UTC date.

The resolver selects the latest-starting assignment if inconsistent overlapping data somehow exists. It then falls back through the tenant default policy to employee-profile values.

No reviewed frontend displays this resolution, collects ranges, calls the diagnostic endpoint, or explains the selected source.

Source References

• microservices/src/attendance-service/Domain/TimeOffice/EmployeeShiftAssignment.cs
• microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
• microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
• microservices/src/attendance-service/Application/Services/ShiftPolicyQueries.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsx

Related Articles

• UI and operations overview
• Known limitations
• Source map

See Also

• Events documentation
• API documentation
• Technical documentation

Keywords

• Workforce Scheduling UI
• Shift administration
• Scheduling operations

Revision Information

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