Version 389

Updated by Leigh Hutchens

Release date December 2, 2020

Don't forget that mobile access rights is available in Neo now. Read more about how to get it up and running for your organization here!

Upcoming release dates

To ensure the best possible support for our customers for releases to RC and Production over the Christmas and New Year's holidays, we've made the following changes to the release calendar:

  • Core-391/Neo-98 release to RC moved from December 24 to December 21, 2020
  • Core-391/Neo-98 release to Production moved from December 30 to December 29, 2020
  • Core-392/Neo-99 release to RC from January 7 to January 4, 2021
  • Core-392/Neo-99 release to Production untouched and stays as planned January 13, 2021

New functionality

Check out new functionality in Neo here!

Updates and performance improvements

Minus time on last day of period

Minus time is now generated on the last day of the selected period instead of the last day in the period containing a punch. This will allow for minus time to be generated within the correct period regardless of the period selected within transfer to payroll matches the period of the minus time calculation.

In Classic, a virtual shift will "hold" the generated minus time:

In Neo, it will be visible on the Time card in the Salary type overview:

It's also reflected in the statistics related to salary cost for the day it is generated on (last day of period). It will not be shown in the TTP view, but will, of course, be transferred to payroll and visible in all reports done from analytics.

Performance improvements

  • General performance improvements within processing of salary types.
  • General performance improvements within generation of payroll files.

Bug fixes

  • Correction to Employees missing in Payroll Report using “Only approved time punches”.

API / Web service updates

The following SOAP API endpoints will be discontinued and removed from Quinyx WFM mid January 2021 (planned for 2021-01-13)

  • 7.3 wsdlGetUserDefinedFields
  • 7.4 wsdlUpdateUserDefinedFields
  • 7.5 wsdlGetUserDefinedFieldValues
  • 7.6 wsdlUpdateUserDefinedValues
  • 7.7 wsdlGetUserDefinedShifts
  • 7.8 wsdlUpdateUserDefinedShifts
  • 5.2 wsdlUpdateCrmCustomers
  • 5.4 wsdlUpdateCrmRoles
  • 5.5 wsdlUpdateCrmOrders
  • 5.6 wsdlGetCrmDecisions

The following SOAP API endpoints will be discontinued and removed from Quinyx WFM August 2021.They are already now replaced with REST API endpoints for Neo Forecast. Read more about Neo Forecast and the improved functionality here and about the new REST APIs here.

  • 6.2 wsdlGetForecasts
  • 6.3 wsdlUpdateForecasts
  • 6.6 wsdlUpdateForecastV2
  • 6.8 wsdlUpdateForecastsV3
  • 6.4 wsdlGetSalesData
  • 6.9 wsdlGetSalesDataV2
  • 6.7 wsdlGetOptimalStaffing
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 make sure 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 SOAP APIs. These restrictions will be enforced programmatically and means that we will enforce a limit on concurrent calls per customer to 10. You should expect response code 429 if you happen to exceed this limit and you are recommended to implement a backoff-retry mechanism to handle the limit. We will start by introducing the limit at a higher level which will not affect any customers’ usage on RC for testing purposes within the next month and on Production January 14th. The limit of 10 concurrent calls will be introduced on RC January 21st and on Production February 10th.Note that the limit applies to SOAP only. When moving from SOAP to Rest over the following years, any limits will be built into the API. Please make sure to forward this information to the party within your company responsible for integrations.


How Did We Do?