Helpdesk Document Integration Boundary

Finding

Document Service interaction is synchronous HTTP, not event-driven. No Document Service consumer of HelpdeskTicketEvent was found, so an event-driven document diagram is intentionally omitted.

Helpdesk uploads or downloads attachment content through a typed client. After a successful upload result, the endpoint creates local attachment metadata, audit/timeline evidence and TicketAttachmentAdded in the Helpdesk outbox. The attachment event informs notification behavior; it does not command Document Service storage.

Attachment deletion removes the local attachment record and writes audit/timeline evidence, but no attachment-removed integration event is emitted.

Failure boundary

An unavailable or invalid upload response prevents the successful attachment mutation and therefore prevents TicketAttachmentAdded from being queued. Development fallback behavior exists in the client, but environment enablement is outside this event contract.

Source References

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

Related Articles

• Events landing page
• Event limitations
• Event source map

Revision Information

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