Onboarding & Offboarding UI and Operations Known Limitations
Summary
The lifecycle experience is usable but Transitional. These limitations are source-verified gaps, not commitments or inferred defects in a particular deployment.
Audience
Product, architecture, security, QA, support and engineering teams.
Reference Content
| Area | Verified limitation |
|---|---|
| Lifecycle experience | Onboarding and exit are separate workspaces with no unified coordinator or end-to-end readiness view |
| Routing | The same UI can reach extracted or compatibility implementations with different persistence semantics |
| Onboarding validation | Email, phone, bank, KYC and credential-strength validation is limited; checklist completeness is not a hard gate |
| Credential UX | The UI can generate/reveal temporary credential material and show returned credentials after completion |
| Form safety | No verified dirty-form warning or draft persistence; cancellation clears current onboarding selection |
| Responsive UI | Onboarding uses minimum-width columns and exit uses wide tables without verified lifecycle-specific small-screen behavior |
| Accessibility | No lifecycle-specific automated accessibility evidence was found |
| Offer response | Client validation for signer name/signature is not verified; error feedback for failed public actions is limited |
| Exit navigation | Protected Exit route exists without a verified current menu entry |
| Exit rollback | Review controls exist, but no employee rollback-request control is exposed |
| Exit scope | No coordinated exit interview, knowledge transfer, final settlement, archival or asset-clearance workspace |
| Access revoke | Processing is a manual confirmed action and is not shown as scheduled/automatic |
| Partial load errors | Exit startup suppresses some individual source failures, allowing partially empty UI |
| Reporting | No dedicated offboarding analytics/report/export surface; dashboard values can use client-derived fallbacks |
| Event delivery | Recruitment registers an outbox relay; Employee event relay registration is not verified |
| Cross-domain integration | Attendance and Asset are not verified Employee-lifecycle event consumers; Notification coverage is limited |
| Operations | No lifecycle-specific SLO, alert definition, synthetic journey, on-call model or production runbook is verified |
| Automated testing | No focused UI test suite for these two lifecycle pages was found in the inspected frontend source |
Security-sensitive UI behavior should be remediated before treating temporary credentials or public action links as support artifacts. Environment-specific mitigations Require confirmation.
Source References
UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsxUI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsxmicroservices/src/gateway-api/Program.csmicroservices/src/employee-service/Program.cs
Related Articles
See Also
Keywords
- Known limitations
- Transitional
- Lifecycle gaps
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly