Ignore an offboarding
Discard a pending offboarding: cancels it with the open tasks of its ticket, clears the last day of the employee and gives them back their access, so they stay in the company. Only a PENDING offboarding can be ignored (ONLY_PENDING_OFFBOARDING_CAN_BE_IGNORED otherwise): once a step has started, cancel the remaining tasks with updateTaskStatus. Refused with OFFBOARDING_NOT_FOUND for an offboarding of another company.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Path Parameters
Response
Whether the offboarding runs on the steppers from before offboarding tickets
PENDING, SCHEDULED, IN_PROGRESS, CLOSED, CANCELED COCKPIT, MERGE, KOMBO, API ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$The offboarding ticket, whose tasks are its steps (getTicket)
The reference the cockpit shows for that ticket
How the offboarding holds its steps: ACTIONS (the steppers from before offboarding tickets) or INTENTS (typed tasks under its ticket, run through the intent tools such as executeOffboardingConfirmationIntent). Null while it has neither a ticket nor a step.
ACTIONS, INTENTS