Skip to main content

Performance UI Validation and Feedback

Summary​

Client validation covers required cycle fields, appraisal cycle/employee selection, and goal appraisal/title selection. Compatibility validation requires an employee and goal title. Numeric fields are converted but complete range and lifecycle validation remains server-owned.

Mutation success uses toast feedback and reload. Canonical workspace load failures use an error surface with retry. Report cards isolate unavailable responses. Domain validation covers cycle date/name/state, editable goal state, required goals before self submission, ordered review stages, approval, close, and reopen state.

The UI does not consistently disable impossible lifecycle actions in advance; server rejection remains expected.

Requires confirmation​

Fine-grained role policy, accessibility conformance, production support ownership, and long-term compatibility behavior 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/pages/hr/HrOperationsPage.tsx
  • microservices/src/performance-service/Domain/Appraisal/Appraisal.cs
  • microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.cs

See Also​

Keywords​

  • Performance UI
  • Draft documentation

Revision Information​

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