# PutAbsenceByAbsence Edit the details of a Absence __Activity name :__ PutAbsenceByAbsenceId __Metadata :__ Possible options for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the PUT URL. Edit the details of am Absence Select loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId} Insert loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId} Update loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId} Delete loket.nl (REST) API URL: /providers/employers/employees/absences/{absenceId} Select loket.nl (REST) API Operation: put /providers/employers/employees/absences/{absenceId} - 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 `PutAbsenceByAbsence` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `accidentType_key` | `int32` | | ☐ | The key of the accident type. Possible values can be aquired via the metadata endpoint. | | `accidentType_value` | `string(50)` | | ☐ | Description of the accident type. | | `actionToBeTakenByOccupationalHealthAndSafetyService_key` | `int32` | | ☐ | The key of the desired action to be taken by the occupational health and safety service. Possible values can be aquired via the metadata endpoint. | | `actionToBeTakenByOccupationalHealthAndSafetyService_value` | `string(50)` | | ☐ | Description of the desired action to be taken by the occupational health and safety service. | | `caseManager_function` | `string(50)` | | ☐ | Function of the case manager. | | `caseManager_name` | `string(25)` | | ☐ | Name of the case manager for reintegration. | | `caseManager_organization` | `string(70)` | | ☐ | Function of the case manager. | | `caseManager_phoneNumber` | `string(15)` | | ☐ | The phone number of the employee. | | `causeOfAbsence_key` | `int32` | | ☐ | The key of the cause of the absence. Possible values can be acquired via the metadata endpoint | | `causeOfAbsence_value` | `string(50)` | | ☐ | Description of the cause of the absence. | | `comments` | `string(4000)` | | ☐ | Free text field to register any relevant information. | | `contactInformation_city` | `string(24)` | | ☐ | City of the address | | `contactInformation_country_isoCode` | `string(2)` | | ☐ | The ISO 3166-1 alpha-2 value for the country | | `contactInformation_country_key` | `int32` | | ☐ | The key for the country. Posible values can be aquired via the metadata endpoint | | `contactInformation_country_value` | `string(50)` | | ☐ | The name of the country | | `contactInformation_endDate` | `datetime` | | ☐ | end date of the contact information | | `contactInformation_furtherIndication_key` | `int32` | | ☐ | The key of the further indication. Posible values can be aquired via the metadata endpoint | | `contactInformation_furtherIndication_value` | `string` | | ☐ | The description of the further indication, the posible values are "WW" and "AB" | | `contactInformation_houseNumber` | `int32` | | ☐ | House number of the address | | `contactInformation_houseNumberAddition` | `string(4)` | | ☐ | An addition to further specify the house/door/postbox. For example used to specifty a room of floor number in addition to the house number. | | `contactInformation_locationType_key` | `int32` | | ☐ | The key of the location type. Posible values can be aquired via the metadata endpoint | | `contactInformation_locationType_value` | `string(50)` | | ☐ | Description of location type | | `contactInformation_name` | `string(70)` | | ☐ | name of the institute for the contact information. | | `contactInformation_phoneNumber` | `string(15)` | | ☐ | The phone number to contact the employee on. | | `contactInformation_postalCode` | `string(9)` | | ☐ | The postal code of the address | | `contactInformation_startDate` | `datetime` | | ☐ | start date of the contact information | | `contactInformation_street` | `string(24)` | | ☐ | Streetname of the address | | `expectedDateOfChildbirth` | `datetime` | | ☐ | Date of Delivery | | `expectedDuration_key` | `int32` | | ☐ | The key of the expected duration of the absence. Possible values can be acquired via the metadata endpoint. | | `expectedDuration_value` | `string(50)` | | ☐ | Description of the expected duration of the absence. | | `expectedEndDateOfMaternityLeave` | `datetime` | | ☐ | expected end date of pregnancy leave | | `hasMobilityIssue` | `boolean` | | ☐ | This field indicates whether the Employee has an issue limiting its mobility. | | `hoursWorkedOnFirstDayOfAbsence` | `int64` | | ☐ | The number of hours worked on the first day of the absence. | | `id` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `isDisruptedEmploymentRelationship` | `boolean` | | ☐ | Indicates whether the employement relationship between employee and employer is disrupted. | | `isHospitalised` | `boolean` | | ☐ | Does this concern a hospital admission | | `isRecoveredWithinTwoWeeks` | `boolean` | | ☐ | This field indicates whether the Employee is (expected) recoverd within two weeks, relating to a full recovery. | | `isThirdPartyLiability` | `boolean` | | ☐ | This field is related to `accidentType`. When `accidentType` is specified, this field indicates whether a third party is liable for the accident. | | `isWorkRelatedIllness` | `boolean` | | ☐ | Occupational disease | | `progress_currentIncapacityPercentage` | `int64` | | ☐ | percentage of not being able to work | | `progress_endOfAbsence_date` | `datetime` | | ☐ | The last day of the absence. | | `progress_endOfAbsence_reason_key` | `int32` | | ☐ | The key of the reason why the absence is ended. Possible values can be aquired via the metadata endpoint. | | `progress_endOfAbsence_reason_value` | `string(50)` | | ☐ | Description of the reason why the absence ended. | | `progress_startDate` | `datetime` | | ☐ | start dat of the incapacityPercentage | | `reintegration_dateOfFinalizingPlanOfAction` | `datetime` | | ☐ | The day on which a plan of action (for return to normal work) was finalized. | | `reintegration_reintegrationGoal_key` | `int32` | | ☐ | The key for the reintegration goal. Related to the Wet Verbetering Poortwachter. | | `reintegration_reintegrationGoal_value` | `string(50)` | | ☐ | The name of the country |