Attendance UI Validation and Error Messages

Summary

UI validation combines client checks, readonly-state evaluation, protected-route behavior, and backend error responses.

Frontend/backend developers, QA engineers, support engineers, and product owners

Area	Confirmed UI behavior	Authority
Missing tenant / permission	Protected route or API error	Guard plus backend
Missing employee	Selection/self-context checks	UI plus backend
Invalid/future/readonly date	Day-cell readonly reason; reopen server restriction	UI plus backend
Duplicate Attendance	No dedicated client check	Backend/application; Requires confirmation
Invalid hours	Numeric/form schema checks are partial	Backend
Invalid Shift/policy	Required name and threshold ordering checks	UI plus backend
Overlapping assignment	No assignment UI	Backend only
Missing profile	Roster/employee context may be absent	Safe empty/error state
Payroll lock	Reopen approval API error	Backend
Invalid transition	Action availability plus API error	Backend
Duplicate/future reopen	API-derived error	Backend
Network/server failure	Inline error and toast fallback	UI
Permission denied	Unauthorized page or API error	Guard plus backend

Exact backend messages can differ between compatibility and extracted-service paths; tests should assert categories unless a contract fixes the text.

UI/salary-ui/apps/client-hrms-portal/src/pages/AttendanceStatus.tsx
UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx
microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs