Forms and Validation

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

Form	Client validation	Server validation affecting the UI
Shift	Nonblank name; nonnegative numeric inputs through HTML constraints	Required payload, time parsing, unique active name, domain ranges
Attendance policy	Nonblank name; half-day threshold cannot exceed full-day threshold; nonnegative numeric inputs	Required payload, unique active name, threshold and rule invariants, single default
Fixed shift on employee	Option selection including no fixed shift	Employee-form validation and referenced record behavior
Effective assignment	No UI	Valid employee and active shift, valid dates, no overlapping active range
Weekly offs	Toggle from the seven day choices	Valid unique day values

Errors are rendered as a shared inline message; policy successes also use toast messages. Shift saves do not show a dedicated success toast. The page does not disable submission while saving and does not provide field-level server error mapping.

Source References

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

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