Skip to main content

Gateway Boundaries

Audience​

Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling API behavior and boundaries.

Summary​

Gateway routing independently controls the shift-policy compatibility slice. This allows shift, weekly-off, and attendance-policy administration to move to Attendance Service without moving the broader Attendance API.

Routing behavior​

The shift-policy decision is evaluated before broader Attendance and Leave ownership. When enabled, all three compatibility families route to Attendance Service. When disabled, shifts return to the monolith and weekly offs fall through to their existing owner. A higher-priority policy route is added during shift-policy ownership because the monolith has no policy counterpart.

A prefix-stripping shadow route allows direct compatibility exercise without changing ownership. Gateway middleware records the selected route source and forwards correlation and caller context.

Frontend behavior​

The frontend calls compatibility-relative paths through its shared API client. It does not select the backend owner. Shift management consumes shift CRUD and policy administration; labor and user management read shifts; attendance and payroll screens read weekly offs.

Classification​

Gateway exposure is Transitional. Edge authentication, header sanitization, and production ownership state require confirmation.

Source References​

  • microservices/src/gateway-api/Program.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsx

See Also​

Keywords​

  • Workforce Scheduling API
  • Shift endpoints
  • Attendance policy API

Revision Information​

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