Skip to main content

Helpdesk Event Overview

Summary​

Each supported lifecycle operation constructs a fresh HelpdeskTicketEvent and serializes it into an outbox row. The event name is data in the shared contract rather than a distinct CLR contract for each lifecycle action.

Ownership and boundaries​

  • Helpdesk Service: owns lifecycle triggers, payload projection and outbox persistence.
  • Shared contracts: owns IntegrationEvent and HelpdeskTicketEvent.
  • Shared kernel: owns serialization, the processor abstraction and broker publisher.
  • Notification Service: subscribes to all ten names and resolves notification intents.
  • Document Service and Gateway: participate through synchronous HTTP boundaries, not Helpdesk event consumption.
  • External consumers: none were verified.

Maturity​

Contract construction and transactional persistence are implemented. Automatic Helpdesk relay execution is missing. Notification consumption is implemented independently, so the overall integration is Partial.

Requires Confirmation​

Deployment-level relay substitution, operational broker enablement, downstream consumers beyond Notification Service, and schema-evolution governance require confirmation.

Source References​

  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
  • microservices/src/helpdesk-service/Infrastructure/Persistence.cs
  • microservices/src/helpdesk-service/Program.cs
  • microservices/src/contracts/Events/HelpdeskLifecycleEvents.cs

Revision Information​

Draft source-backed documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.