Helpdesk Gateway Boundaries

Audience

Developers, QA, security, support and architects.

Summary

Gateway behavior has three Helpdesk paths: configurable compatibility ownership, a shadow prefix for the extracted service and employee handlers that directly call canonical ticket operations.

Reference Content

Employee GET forwarding adds no requester predicate. Employee POST forwarding requires a body but does not translate category/priority names to canonical identifiers. The broader employee dashboard includes Helpdesk as one downstream component but is excluded from the Helpdesk endpoint count.

Requires confirmation

Production ownership selection, shadow-route exposure, gateway authentication, requester scoping and employee contract transformation require confirmation.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/gateway-api/EssEndpoints.cs
• UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx

Related Articles

• API overview
• Endpoint catalog
• API limitations

See Also

• Technical documentation
• API source map

Keywords

Gateway routing, compatibility cutover, employee gateway, shadow route.

Revision Information

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