Operations Overview

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

Operational dependencies are the authenticated client session, gateway routing, the selected backend owner, tenant context, and persistence. Attendance Service also starts its outbox relay, although scheduling changes do not publish events.

No scheduling-specific runbook, SLO, alert, maintenance page, support escalation rule, backup procedure, or in-product operator console was found. Ownership is represented by the Attendance code boundary and documentation metadata; production operational ownership requires confirmation.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/attendance-service/Program.cs
• microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.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