Helpdesk Compatibility Architecture

Audience

Developers, QA, support and architects.

Summary

Compatibility exists at routing, API projection, identity and data-migration levels. Canonical ticket identifiers coexist with numeric compatibility identifiers.

Reference Content

The gateway defaults HR Suite Helpdesk ownership to the legacy route unless configured otherwise. Employee-service handlers address the extracted Helpdesk route directly. Compatibility endpoints translate legacy-shaped records to canonical tickets, while the offline backfill creates/updates canonical rows and validates count groupings.

Requires confirmation

Current routing selection, cutover acceptance, parity semantics, rollback ownership and compatibility retirement criteria require confirmation.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Backfill/HelpdeskBackfill.cs
• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

Compatibility routing, gateway cutover, legacy projection, backfill.

Revision Information

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