PutAbsenceContactHistoryByAbsenceContactHistoryId |
Edit the details of a contact history__Activity name :__ PutAbsenceContactHistoryByAbsenceContactHistoryId__Metadata :__ Possible options for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the PUT URL.Edit the details of a contact history
Catalog: LoketNlRest
Schema: ContactHistory
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.
Select loket.nl (REST) API URL: /providers/employers/employees/absences/absencecontactHistory/{absencecontactHistoryId}
Insert loket.nl (REST) API URL: /providers/employers/employees/absences/absencecontactHistory/{absencecontactHistoryId}
Update loket.nl (REST) API URL: /providers/employers/employees/absences/absencecontactHistory/{absencecontactHistoryId}
Delete loket.nl (REST) API URL: /providers/employers/employees/absences/absencecontactHistory/{absencecontactHistoryId}
Field Selection Method: NotRequired
Base Path: content
Select loket.nl (REST) API Operation: put /providers/employers/employees/absences/absencecontactHistory/{absencecontactHistoryId}
Table Function Parameters
The following parameters can be used to control the behaviour of the table function PutAbsenceContactHistoryByAbsenceContactHistoryId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be treated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example with `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.
Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.
Name |
Data Type |
Required |
Default Value |
Documentation |
---|---|---|---|---|
absencecontactHistoryId |
guid |
☑ |
|
The unique identifier of the record |
body |
string |
☑ |
|
Absence progress to edit. |
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). |
Table Function Columns
The columns of the table function PutAbsenceContactHistoryByAbsenceContactHistoryId are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
---|---|---|---|---|
contactDate |
datetime |
|
☐ |
The date on which the contact was initiated. |
contactMethod_key |
int32 |
|
☐ |
The key of the method of contacting the employee |
contactMethod_value |
string(50) |
|
☐ |
Description of the method of contact. |
id |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
summary |
string(4000) |
|
☐ |
Summary of the contact. |
13-05-2022 15:37 Version 22.1.40-BETA+3374