Allows you to read the daily schedule assignments for each employee. In particular, it shows the employee's contracted working time and contracted working periods.
Reading daily schedule and working periods assignments
Link to WSDL: https://sandbox-ws.kelio.io/open/services/DailyScheduleAssignmentService?wsdl
Web Service: DailyScheduleAssignmentService
Method: exportDailyScheduleAssignmentsList
|
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: the list of schedule assignments for 02/08/2024 and 03/08/2024 Enter text here
|
||||
Writing daily schedules and working periods assignments
Method to be used to update the employee’s schedule on a day.
Link to WSDL: https://sandbox-ws.kelio.io/open/services/DailyScheduleAssignmentService?wsdl
Web Service: DailyScheduleAssignmentService
Method: importDailyScheduleAssignments
Employee’s ID: •By identification number: employeeIdentificationNumber •Or by badge: employeeBadgeCode •Or by Surname/First name: employeeSurname and employeeFirstName
Schedule identifier: •Schedule abbreviation: dailyScheduleAbbreviation •Schedule description: dailyScheduleDescription •Assignment date: assignmentDate
|
|
|
|
||||
If a request is made to write data to Kelio: •If there is no error, the Web Service returns an empty request with no elements. •If there are errors when writing data, the Web Service returns the elements in error and populates the field errorMessage. The message returned corresponds to the description of the functional error encountered by the Web Service during the data write request.
|
||||||||
Created with Help+Manual 9 and styled with Premium Pack Version 5 © by EC Software
