Helpdesk Attachment Model

Audience

Developers, QA, security, support and architects.

Summary

TicketAttachment stores metadata and external document/storage identifiers; Helpdesk does not store production file bytes in its relational model.

Reference Content

Fields include ticket identity, document and storage-object identifiers, storage key, filename, content type, byte size, SHA-256 value, uploader and creation time. EF Core limits text sizes and indexes tenant/ticket/time.

Upload and download delegate to the document client. The Helpdesk delete handler removes only the local attachment row; the reviewed document client exposes no delete operation. A development-only filesystem fallback can store/download bytes when explicitly enabled.

Requires confirmation

External file deletion/retention, malware scanning, metadata trust, cleanup after partial failure and fallback-file cleanup require confirmation.

Source References

• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs
• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

TicketAttachment, document identifiers, SHA-256, file metadata, deletion.

Revision Information

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