Version 392

Updated by Leigh Hutchens

Release date January 13, 2021

Last Classic release notes

From the next planned release of Quinyx WFM, there will be only one set of release notes.

New functionality

Nothing new here. Please check the Neo version 0099 release notes.

Updates and performance improvements

Some SOAP API endpoints have been discontinued and removed. Read more in the section API / Web service updates below.

Bug fixes

  • Correction to Salary on tasks not giving the correct output in combination with "Punched Hours" in the shift type rule.

API / Web service updates

The following SOAP API endpoints will be discontinued from this release as previously stated

  • 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?