Terminations

What termination does: ends the work relationship, sets the termination date, changes assignment statuses, triggers de-provisioning, and starts downstream processes. The date questions. Notification date, termination date, last working day and final pay date can all differ. Configure them, and — more importantly — communicate which is which, because four dates with similar names is how the wrong one ends up on a statutory form. Voluntary versus involuntary matters for reporting and, in some jurisdictions, for statutory obligations. And what termination does not do: it does not delete the person, and it does not necessarily remove all access immediately — check the de-provisioning configuration from the security module, because that gap is one of this module's failures. Then the build: terminate a worker with a reason and review the resulting statuses; see the effect on the manager hierarchy for their reports; look at the employer comments report and at what…

In this module: Module 11 · The Action Framework, Employment Flows and Terminations

1. 1The action framework
2. 2Configuring actions and action reasons
3. 3Guided flows and Transaction Design Studio preview
4. 4Approvals for employment transactions
5. 5Hire, promote, transfer
6. 6Terminations
7. 7Reversing and correcting employment errors
8. 8Checking employment data issues
9. 9What breaks
10. 10Lab: run the employment lifecycle end to end