Version 383

Updated 1 month ago by Leigh Hutchens

Release date September 9, 2020

Hi! As you might know, we are busy building Neo, a completely new web interface for managers. Neo will replace Classic at the end of this year, when all major modern browsers will drop support for Adobe Flash. Until then, we are turning off certain views in Classic to encourage managers to use the improved version of the view in Neo.

This change will also impact how we'll handle bugs in Classic until it is retired. In short, we won't investigate or resolve any bugs in Classic unless they have a direct impact on payroll outcome as defined in our Service Level Agreement (SLA).

Instead, we'll focus our efforts on the Neo roadmap and feature list to enhance the user experience and to ensure that Neo offers functionality beyond the capabilities of Classic as soon as possible.

Read more about the Neo roadmap and feature list here.

New functionality

Possibility to set an external ID on a Neo role

You can now set an external Neo role ID from Classic > Settings > Tables > Integration key types / Integration keys. In this version, we also release API support in the endpoints wsdlUpdateEmployees and wsdlGetEmployeesV2.

Read more about configuring integration key types and integration keys here.

Updates and performance improvements

  • The label "Time" on the Time card has been replaced with "Amount".
  • General performance improvements relating to skills.

Bug fixes

  • Added prevention of deletion of a Time Tracker when still connected to a salary type.

API / Web service updates

wsdlUpdateEmployees : Now supports extNeoRoleId as compliment to RoleId when setting groupRoles in the request.

wsdlGetEmployeesV2 : Now supports extNeoRoleId as well as neoRolesIds when using includeNeoRoles.

Click here to view the new Quinyx WFM Web Service documentation. You can find even more web services info here.
We encourage all our customers to make use of our APIs to maintain data and to ensure that information is up-to-date. To ensure scalability of our APIs while growing our customer and user base, we have decided to add restrictions on usage of our APIs. These restrictions will be enforced programmatically. We are currently monitoring usage of our APIs to identify which restrictions will be necessary to ensure performance over time.The first limit will be related to number of concurrent calls which will be set to 5. You should expect response code 429 if you happen to exceed this limit. We will inform you when this limit and any additional limits will be enforced in upcoming release notes so you have time to make any necessary changes to your clients.


How Did We Do?