Helpdesk Validation Architecture

Audience

Developers, QA, security and support.

Summary

Validation is distributed across value objects, endpoint helpers/branches, EF Core constraints and limited client checks. No FluentValidation or dedicated validator classes were found.

Reference Content

• Ticket number, title and SLA duration use domain value objects.
• Endpoints validate tenant, referenced records, enum parsing, required comment text, attachment size and selected SLA conditions.
• EF Core enforces required fields, lengths and selected tenant-scoped uniqueness.
• The admin UI checks comment input and uses browser-parsed assignee values.
• Employee UI requires title/description but sends classification names that do not match canonical identifiers.

The generic status handler validates only that the requested value is defined; it does not enforce a current-to-next transition.

Requires confirmation

Unified validation strategy, problem-details format, frontend/service contract alignment, identity validation and lifecycle rules require confirmation.

Source References

• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Application/Common.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
• UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

Validation architecture, value objects, endpoint validation, EF constraints.

Revision Information

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