Frequently Asked Questions

Summary

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

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

Where are shifts configured? On the protected Shift Management route, reachable from Workforce, Settings, or the Settings Hub when entitled.
Is there a roster planner? No verified roster or calendar planning screen exists.
Can the same page manage attendance policies? Yes. Its second section creates and edits policies.
Can an administrator assign a dated shift range in the UI? No. Only legacy fixed-shift selectors are implemented; dated assignments are API-only.
What happens when assignment ranges overlap? The extracted command rejects overlapping active inclusive ranges.
How is the effective policy chosen? Active dated assignment and shift, then active tenant default policy, then employee profile.
Can employees see or swap future shifts? No verified self-service schedule or swap workflow exists.
Why might two environments behave differently? A gateway cutover toggle can select the legacy or extracted owner for scheduling compatibility traffic.
What monitoring exists? Basic health, route/correlation logs, relay warnings, and persisted audit/timeline diagnostics; no scheduling dashboard or alert was found.
Are scheduling notifications implemented? No verified scheduling notification contract, template, or UI was found.

FAQ total: 10 evidence-backed entries.

UI/salary-ui/apps/client-hrms-portal/src/App.tsx
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/Application/Services/AttendancePolicyResolver.cs
microservices/src/gateway-api/Program.cs