Helpdesk Entity Mappings

Audience

Developers, database engineers and QA.

Summary

All mappings are configured centrally in HelpdeskDbContext rather than separate configuration classes.

Reference Content

Tenant-derived entities share key, tenant-key length, tenant index and query filter configuration. Ticket number/title and SLA duration use value conversions. Status/level/target/escalation enums use string conversions. Metadata, activity details and event payloads use structured JSON storage.

Required constraints are explicitly configured for selected names, ticket values, comment body, attachment references/metadata, escalation reason, activity descriptors and outbox payload/status. Optionality otherwise follows nullable CLR types and migration output.

Only the three Ticket child relationships have explicit cascade deletion. No precision configuration is present because no monetary decimal persistence is mapped.

Requires confirmation

Mapping conventions, nullable-reference enforcement, future configuration-class separation and precision needs require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/HelpdeskDbContextModelSnapshot.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Fluent mapping, required field, optional field, JSON, cascade delete.

Revision Information

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