LMS UI Validation

Summary

The admin workspace performs presence checks for selected forms; backend validation and lifecycle checks remain authoritative.

Reference Content

Surface	UI validation	Backend boundary
Course	Code and title required	Normalization, length, uniqueness, lifecycle
Learning path	Name required	Tenant persistence and course relationships
Enrollment	Course and employee-user reference required	Published course, lifecycle state, uniqueness
Assessment	Course and title required	Course existence, numeric bounds, attempt state
Session	Course, title, start, end required	Course existence and persistence
CSV	Non-empty content required	Schema and row validation
Certificate	No preflight form validation	State and document rules

Error handling is primarily toast-based for local validation and a shared page error banner for load failures. Mutation exceptions rely on shared request handling; field-level server errors are not mapped to individual controls.

Screenshot placeholder

No sanitized screenshot is committed. Capture only non-production, non-personal demonstration data during an approved documentation review.

Requires confirmation

Fine-grained authorization, accessibility conformance, responsive acceptance criteria, and long-term product ownership require confirmation where not source-backed.

Source References

• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx
• UI/salary-ui/apps/client-hrms-portal/src/App.tsx
• microservices/src/training-service/Domain/TrainingEntities.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs

Related Articles

• LMS UI documentation
• LMS API documentation

See Also

• Navigation
• UI testing

Keywords

• LMS UI
• LMS UI Validation

Revision Information

• Status: Draft
• Last reviewed: 2026-07-17
• Review cycle: Quarterly