Helpdesk Forms & Validation

UI validation matrix

Form/action	Client validation	Server validation relevant to UI
Employee create	Nonempty title and description	Valid title; existing category/priority IDs; tenant context
Assignment	Text-to-integer conversion; no required check	Ticket existence; assignment values persisted
Internal comment	Trimmed comment must be nonempty	Required body; author can fall back to tenant/requester context
Resolve/close/reopen	No input form; portal sends fixed text	Ticket existence and status parsing in shared status path
Search/filter	No server validation; browser filtering	Not applicable
Attachment download	No prevalidation	Ticket/attachment/document existence and service availability

The employee inputs do not use category or priority selectors and do not align with the canonical GUID-based contract. The assignment converter maps blank user ID to zero. No email-format validation is applied. Lifecycle action promises are not wrapped by local error handling, so failure feedback depends on shared client behavior and may not produce a screen-specific message.

Empty queue and attachment tables show “No records found.” The admin page shows an error banner with Retry for initial load failure; secondary category, priority, report and attachment failures are intentionally degraded.

Source References

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

Related Articles

• UI and operations landing page
• Known limitations
• Source map

See Also

• Events documentation
• API documentation
• Technical documentation

Keywords

Helpdesk, employee service desk, ticket UI, operations, diagnostics.

Revision Information

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