CalculatedLeaveHoursByEmploymentId_ContentSpecification |
Get the number of leave hours for start to enddate__Activity name :__ GetProposedLeaveHoursByEmploymentId<span style="color:red">========== This enpdoint is still under development and cannot be used yet. Subscribe to the newsletter to receive updates. ==========</span>Returns the numberOfHours (only in hours) calculated based on the employments working- hours/schedual __Note:__ The function will only work if the employment is either linked to no leave policy or linked to only leave policy(s) that use hours as the unit of leave.Further more how the leave hours are calculated can be managed in the leave policy with the `applyLeaveSchedule` and `working hours` resource with the field `calculateUsingWorkPattern.leaveHours` The order is as follows. If calculateUsingWorkPattern.leaveHours is true the work patern from workinghours is used otherwise if applyLeaveSchedule is set to true the `leavePattern` is used otherwise the workinghours are used
Catalog: LoketNlRest
Schema: Leave
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}/leave/calculateLeaveHours
Insert loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/leave/calculateLeaveHours
Update loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/leave/calculateLeaveHours
Delete loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/leave/calculateLeaveHours
Field Selection Method: NotRequired
Base Path: content.specification[*]
Select loket.nl (REST) API Operation: get /providers/employers/employees/employments/{employmentId}/leave/calculateLeaveHours
Table Function Parameters
The following parameters can be used to control the behaviour of the table function CalculatedLeaveHoursByEmploymentId_ContentSpecification. 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 |
endDate |
string |
☑ |
|
The end date |
startDate |
string |
☑ |
|
The start date |
Table Function Columns
The columns of the table function CalculatedLeaveHoursByEmploymentId_ContentSpecification are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
---|---|---|---|---|
date |
datetime |
|
☐ |
The start date of the leave requested |
numberOfHours |
double |
|
☐ |
The number of leave units requested |
totalNumberOfHours |
double |
|
☐ |
The number of leave units requested |
25-05-2022 14:15 Version 22.1.46-BETA+3385