Employee Offboarding Schema
Felder
Employee Offboarding Schema
Process record for offboarding an employee (configurable form + workflow state)
stage
Workflow stage. DRAFT = just submitted/not yet processed; HR = waiting on HR to complete person master data (employee_profile incomplete); SECOND_LEVEL = HR done (or skipped), deactivation/return tasks active; DONE = offboarding complete; CANCELLED = aborted. Server-managed by the offboarding orchestration — never client-written via generic PATCH.
DRAFTHRSECOND_LEVELDONECANCELLEDemployeeProfileId
employee_profiles UUID of the exiting employee (set at submit).
ticketId
tickets UUID of the generated offboarding ticket.
submittedById
Internal users UUID of the team lead who submitted the form.
orgUnitId
Org unit / department (Abteilung) of the exiting employee.
displayName
Full name of the exiting employee, for list display.
email
Work email of the exiting employee.
exitDate
Last day of employment (Austrittsdatum).
requestedSystems
Keys of the systems/accounts to deactivate as selected in the form (Confluence, Baramundi, …). Quick-access copy; the canonical source is formData.
formData
Raw submitted values keyed by the configurable form field ids (tenant.settings.offboarding.formDefinition).
missingEmployeeFields
Snapshot of the employee_profile fields that were missing at submit time and routed the ticket to HR (drives the HR person-data tasks).
notes
Free-text remarks (Besonderheiten).
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/employee_offboardings— Liste, paginiert + filterbarGET /api/v1/employee_offboardings/<id>— Einzelne EntityPOST /api/v1/employee_offboardings— AnlegenPATCH /api/v1/employee_offboardings/<id>— Teil-UpdateDELETE /api/v1/employee_offboardings/<id>— Soft-DeleteGET /api/v1/employee_offboardings/<id>/timeline— Audit + Aktivitäten