# PatchReopenAbsenceByAbsenceId Reopen an absence __Activity name :__ PatchReopenAbsenceByAbsenceId When performing a succesfull call to this endpoint, then the absence and the underlying absence progress will we reopend. Both `endOfAbsenceDate` and `endOfAbsenceReason` will be set to null Select loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId}/reopenabsence Insert loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId}/reopenabsence Update loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId}/reopenabsence Delete loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId}/reopenabsence Select loket.nl (REST) API Operation: patch /providers/employers/employees/absences/{absenceId}/reopenabsence - Catalog: `LoketNlRest` - Schema: `Absence` - Field Selection Method: NotRequired - Base Path: `content` This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API. ## Parameters of Table Function | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `absenceId` | `guid` | ☑ | | The unique identifier of an absence | | `If-Match` | `string` | ☐ | | Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations). | ## Columns of Table Function The columns of the table function `PatchReopenAbsenceByAbsenceId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `DUMMY` | `string(1)` | | ☑ | Default column added since the specification specifies that no data is returned. |