Adding values to enums is not considered a breaking change. The employment
paymentTime enum has been extended to allow for arbitrary string values. See the Bug Fixes section for more details.New Features and Improvements
- Absences are finally here! The new Absences endpoints allow you to retrieve information about absences of one or all persons: Absences and Person Absences
- Added a Time Bookings endpoint to retrieve time bookings for all persons, complementing the existing single-person endpoint.
- The new Time Booking Keys endpoint allows you to look up the booking keys that are used in the time bookings and absences.
- Variable payments can now be submitted for payroll processing. Use the new Variable Payments endpoint to post bonuses or other one-time payroll supplements for a payroll contract. They will be forwarded to the payroll administrator for approval.
- Once approved, submitted variable payments are visible via the Variable Payments GET endpoint, which lists all variable payments for a given payroll contract and billing period.
Bug Fixes
- Payment times were incorrectly limited to the four values provided in the standard version. If you have configured a custom payment time in your system, its id will now be returned instead of the enum values.
New Features and Improvements
- Want to know the name of the group a person is in? The new Groups endpoint lets you look up groups by type and returns their names.
To support writing information the access token scope has changed from
api:read to api:use.New Features and Improvements
- Many new fields for the person endpoints:
usualPlaceOfWork,status,groupExitDate,exitReasonId,exitNoticeDate,legalEntity,groups(PAYROLL_COMPANY,TIME_COMPANY,ORGANISATIONAL_UNIT,COST_CENTER,PAYROLL_GROUP,BUSINESS_AREA),keyNumber,employments(personGroupCode,fullTime,permanent,start,end,fixedTermEndDate,workingHours,paymentTime) - The first write endpoint enables you to set and update a person’s private addresses and bank details. PATCH Person By ID
- If you want to take a look at what you’ve written, you can also find the bank details in the person endpoints. Persons - bankDetails
- Resolved the confusing mix of Time Balances and Time Accounts.
- The api returns HTTP status codes 405 (Method Not Allowed) and 406 (Not Acceptable) when a request is made using an unsupported HTTP method or with an unsupported
Acceptheader, respectively. - The api now supports
HEADrequests for all endpoints that supportGETrequests. By definition, these requests will be processed in the same way as GET requests, but no body will be returned.
Bug Fixes
- The persons endpoint no longer returns an error if the VEDA API doesn’t have permission to read any custom fields.
Deprecation
- Deprecated Person#payrollContractIds in favour of the new Person#employments field. Payroll contract IDs are still available in the employments, but the new structure allows for more detailed employment information.
New Features and Improvements
- Improved error handling. Less generic server errors and more 4xx type error responses. Improved and aligned response bodies and codes for invalid request parameters.
- Added support for
customFieldswhen requesting multiple persons. - Changes to non-primal payroll employments are now correctly reflected in person queries using the
modifiedSinceparameter. Empty objects are no longer returned.
New Features and Improvements
- Added support for
additionalAddressInfowhen requesting multiple persons. - The
unitfield in time booking days has been removed, as the day sums are always returned in hours and minutes. - If a data source is needed more than once to answer a query, it’s only accessed once and the result is cached. This improves the performance of larger, more complex requests.
Bug Fixes
- The Time Bookings endpoint now correctly uses the
time-bookingspath instead of the incorrecttimebookings.
Hello World!