Version 390

Updated by Leigh Hutchens

Release date December 17, 2020

Please note this release has been delayed until December 17, 2020 to allow for additional quality assurance.
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 December 21, 2020
  • Core-391/Neo-98 release to Production December 29, 2020
  • Core-392/Neo-99 release to RC January 4, 2021
  • Core-392/Neo-99 release to Production January 13, 2021

New functionality

Check out new functionality in Neo here!

Update to periodized Time Trackers

We've made an update to the periodized Time Trackers when they are configured to use First to expire (Dutch) deduction order. This will allow Time Tracker balances to be shown as two separate balances, even though connected to the same Time Tracker.

The result will be visible in the Mobile application under Salary information for the employee, Absence dialogue in Neo, and Time Trackers in the Time card in Neo.

We'll have an article for you soon that describes how the Dutch deduction order is configured within Quinyx. Stay tuned!

Updates and performance improvements

Payroll report now includes inherited cost centers

The payroll report you can find under Classic > Reports & Statistics > Reports >Time > Payroll report OR Neo > Analytics > Time > Payroll now returns inherited cost centers if are none defined on punch or shift.

If there's a cost center in time punch, and no center in connected shift field “shift cost center”, then cost center will be inherited from time punch and should be marked with '*'
If there's a cost center in time punch, and the time punch is not connected to any shift field, “shift cost center”  will be empty

Bug fixes

  • Absence level is now possible to add with decimals eg 12.5%.
  • Correction to unassigned shifts from deleted employees not possible to be deleted.
  • Correction to reminders sent out every 15 minutes in some cases.

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?