Performance Validation Reference

Summary

Audience

Product, frontend/backend engineering, QA, support, and implementation teams.

Reference Content

Area	Verified rules
Cycle	Tenant and name required; bounded name; end cannot precede start; only Draft opens; Closed cannot reopen; repeat close rejected
Appraisal create	Tenant, cycle, and subject required; cycle must accept appraisals
Goal	Editable appraisal and title required; no aggregate total-weight enforcement
Self review	Editable appraisal with at least one goal
Manager/HR/approval	Exact preceding lifecycle state required; direct path blocked while Workflow-managed
Reopen/close	Reopen only from approved/closed; close only from approved
Workflow callback	Resolvable appraisal, terminal decision, state/idempotency checks, optional instance verification
Compatibility	Goal title required; new record requires employee; reduced mapping rules apply
UI	Required cycle fields, appraisal selection/subject, and goal appraisal/title checks

Server/domain rules remain authoritative when client validation is absent or less strict.

Requires confirmation

Policy ownership, future-state terminology, fine-grained authorization, operational governance, and retirement criteria require confirmation where not implemented.

Source References

• microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.cs
• microservices/src/performance-service/Domain/Appraisal/Appraisal.cs
• microservices/src/performance-service/Domain/Common/ValueObjects.cs
• microservices/src/performance-service/Application/Compatibility/PerformanceCompatService.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx

Related Articles

• Performance reference
• Performance business documentation

See Also

• Technical documentation
• API documentation

Keywords

• Performance reference
• Source-backed catalog

Revision Information

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