Onboarding & Offboarding Business Limitations
Summary
This page consolidates verified gaps and transitional behavior that prevent the documented capability from being treated as one complete lifecycle workflow.
Audience
HR administrators, product owners, engineering, QA, support, security, and architecture reviewers.
Reference Content
The classification table separates process, security, workflow, reporting, integration, notification, compliance, and UI limitations.
| Group | Verified limitation | Classification |
|---|---|---|
| Process | No single end-to-end lifecycle coordinator or shared readiness state | Transitional |
| Process | Employer termination, retirement, contract end, relieving, exit interview, knowledge transfer, final settlement, and archival are absent as governed flows | Not implemented |
| Process | Generic onboarding tasks are not linked to Recruitment onboarding or completion | Foundation |
| Security | Extracted Recruitment endpoints use coarse authorization; action-level onboarding permissions are unresolved | Foundation / Requires confirmation |
| Security | Temporary credential handling is present in the UI/compatibility response; extracted Employee path creates no login | Transitional; security review required |
| Security | Employee document/personal/bank access governance and masking require confirmation | Requires confirmation |
| Workflow | Onboarding and exit do not create reusable Workflow instances | Not implemented |
| Workflow | No delegation, escalation, SLA, reminder, or configurable lifecycle approval | Not implemented |
| Reporting | No consolidated onboarding completeness, readiness, exit, attrition, clearance, or settlement report | Not implemented |
| Integration | Gateway-selected onboarding owners apply different completion fields/outcomes | Transitional |
| Integration | Asset clearance is not wired into offboarding | Foundation |
| Integration | Employee exit does not synchronize Exited to Employee Service Terminated | Not implemented |
| Integration | Payroll/Leave projections do not prove business readiness; Attendance synchronization requires confirmation | Partial / Requires confirmation |
| Notifications | No confirmed onboarding completion, exit submission, rejection, rollback, revoke, or completion notification | Not implemented |
| Notifications | Recruitment onboarding events are not supported by Notification Service consumer | Not implemented |
| Compliance | No verified legal, statutory, retention, consent, identity-verification, or final-settlement compliance policy | Requires confirmation |
| UI | Checklist items are local indicators and notes, not persisted checklist enforcement | Partial |
| UI | No onboarding employee self-service, cancellation UI, asset provisioning UI, or cross-domain readiness view | Not implemented |
| UI | No dedicated offboarding dashboard or integrated clearance actions | Partial |
Public-safety boundary
Never place credentials, personal identifiers, account details, document contents, internal identifiers, storage references, configuration values, internal routes, infrastructure addresses, or operational commands in public evidence. This page states behavior and gaps only.
Source References
microservices/src/recruitment-service/Application/Compatibility/CompatCommands.csmicroservices/src/recruitment-service/Application/Commands/OnboardingCommands.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/asset-service/Application/Queries/AssetQueries.csControllers/HrOperationsController.csUI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsxUI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
Related Articles
See Also
Keywords
- Onboarding limitations
- Offboarding limitations
- Transitional lifecycle
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly