PostTransitionCompensationEmploymentByEmploymentId_Messages |
Create transition compensation employment for existing employment__Activity name :__ PostTransitionCompensationEmploymentByEmploymentIdCreate an additional employment for an already existing and terminated employment with the sole purpose to pay out a transition compensation.
Catalog: LoketNlRest
Schema: CreateEmployment
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/employments/{employmentId}/transitioncompensation
Insert loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/transitioncompensation
Update loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/transitioncompensation
Delete loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/transitioncompensation
Field Selection Method: NotRequired
Base Path: messages[*]
Select loket.nl (REST) API Operation: post /providers/employers/employees/employments/{employmentId}/transitioncompensation
Table Function Parameters
The following parameters can be used to control the behaviour of the table function PostTransitionCompensationEmploymentByEmploymentId_Messages. 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 |
---|---|---|---|---|
employmentId |
guid |
☑ |
|
The unique identifier of the employment |
Table Function Columns
The columns of the table function PostTransitionCompensationEmploymentByEmploymentId_Messages are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
---|---|---|---|---|
code |
int32 |
|
☐ |
Identifying code for the message |
description |
string |
|
☐ |
Describes the message |
id_1 |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
id |
guid |
|
☐ |
In some cases when the message may relate to a specific entity, or specific group of entities, this field provides the identifier of that entity |
type |
string |
|
☐ |
Indication of the type of message.See [the general documentation for more information](./#section/Response/Messages) |
version_obsoleteDate |
datetime |
|
☐ |
The date (can be null) on which the `resourceVersion` is no longer supported/available |
version_resourceVersion |
datetime |
|
☐ |
The resource version of the object in the response |
13-05-2022 15:37 Version 22.1.40-BETA+3374