Reading absence requests
Allows you to read absence requests made by employees between 2 dates. The Web Service returns all the employee's absence requests that have a date period falling within the period requested. Kelio absence requests are independent of absence files. When an absence request is confirmed, the Kelio system creates an absence file. In most cases, absence requests are used to read absences awaiting confirmation. To do this, the status of the request (requestState) is used to identify absence requests awaiting confirmation.
Link to WSDL: https://sandbox-ws.kelio.io/open/services/AbsenceRequestService?wsdl
Web Service: AbsenceRequestService
Method: exportAbsenceRequestsList
|
There are two options for reading employee data: •Either reading an employee's data via one of the employee's identifiers (personnel number, badge no, surname/first name). The ID number is the preferred identifier because it is usually consistent over time. •Or reading data from a list of employees using filters on Population and Group of employees. These concepts can be configured using the Kelio manager (see online help Population and Group). The tag populationMode is used to define this operating mode: populationMode=1: Reading an employee's data In this case, one of the following identifiers is mandatory: •Employee ID number: employeeIdentificationNumber •or Badge code: employeeBadgeCode •or Surname First name: employeeFirstName and employeeSurname •or Technical key: employeeKey (this identifier is used during batch processing after reading employee keys via the Web Service lightEnployee) populationMode=0: Reading data from a list of employees according to Employee Groups and Populations In this case, the concepts of Population and Group can be used. This data is not mandatory. If they are not completed, the Web Service returns the data for all employees. On large quantities of data, this type of request can slow down the performance of the Kelio server. We therefore strongly recommend that you use them. •Population: populationFilter •Group: groupFilter |
Filter on the periods of data to be extracted
There are two ways of filtering dated data by date range. •Either by using a real date period: for example, from 14/05/2024 to 25/06/2024. •Or by using a date range relative to the current date: e.g. -20 days to +10 days.
The tagDateModeis used to define this operating mode:
0: Real date mode Fields to be completed: •startDate: start date using actual date •endDate: end date using actual date
1: Relative date mode Fields to be completed •startOffset: relative start date. Number of days before or after the current date. •endOffset: relative end date. Number of days before or after the current date. |
|
|
|
||||||||
Response to the example request: an absence from 04/08/2025 to 08/08/2025 Enter text here
|
||||
Created with Help+Manual 9 and styled with Premium Pack Version 5 © by EC Software
