Skip to main content

Onboarding & Offboarding Forms and Validation

Summary​

The UI performs a limited set of presence and positive-number checks. Backend validation and authorization remain authoritative; a value accepted by the browser is not proof that the lifecycle action is valid.

Audience​

Lifecycle operators, QA, support and security reviewers.

Reference Content​

Offer and onboarding​

Offer creation requires a candidate, a positive annual compensation value and a joining date. The public rejection action requires a reason. The public accept/sign action does not have verified client checks for signer name or signature text before submission.

Onboarding requires a selected record, employee code, login email, joining date, department and designation. Direct employment requires positive annual compensation; hourly employment requires a positive hourly rate. Designations are filtered by the chosen department.

Optional inputs include phone, employment type, reporting manager, role, temporary credential, bank details, statutory/KYC identifiers, address, notes and documents-submitted state. The UI does not verify full email/phone formats, bank or KYC formats, credential strength, or completion of all readiness checklist items.

The temporary-credential control can generate and reveal a value, and completion feedback can display credential material returned by the server. Operators must avoid screen sharing, copying to tickets or retaining that feedback. The UI generation mechanism is not a verified cryptographic generator.

Exit​

Employee submission requires resignation date, requested last-working date and a nonblank reason. The form does not verify date ordering in the browser. Backend rules decide date validity, active-request conflicts and workflow eligibility.

Approval requires a confirmed last-working date. Rejection and rollback rejection require a reason. The confirmation modal supports Cancel and close actions. Access-revoke processing uses a confirmation modal and is disabled when the UI has no eligible rows.

Errors appear through inline messages and/or toast feedback. Some initial exit data loads deliberately suppress individual request failures, so a partially populated page can appear without a source-specific error. Preserve the correlation reference from an authorized diagnostic context when escalating; never place personal or credential data in a ticket.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/ApprovalActionModal.tsx

See Also​

Keywords​

  • Form validation
  • Required fields
  • Error feedback

Revision Information​

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