Version 0125

Updated 3 months ago by Leigh Hutchens

Release date January 12th, 2022

Upcoming functionality

Upcoming change to Schedule Statistics

We're currently developing functionality to create display groups in Schedule Statistics, similar to that which we have already supported in the Forecast tab. This will allow you to select which variables you want to display in Schedule Statistics, Dashboard, and Forecast Overview, as well as group different data types and variables onto a single graph.

This additional flexibility means that when this functionality is released, users will be required to set up display groups to define which data is accessible in Schedule statistics before they are able to see any variables in Schedule Statistics, including optimal headcount calculations. This must be done by someone with access to Account settings > Variable settings. We will provide more information about how this can be configured closer to the release.

New functionality

None at this time.

Updates and performance improvements

  • We've added a "Select all" option in the filtering menus so that you can easily select all items inside the filter menus.

Bug fixes

  • Resolved an issue that caused hours in statistics to display the wrong number of hours for the wrong time.
  • Resolved an issue that caused a shift to not update correctly after an absence was created and the shift was changed to unassigned.
  • Resolved some various visual issues in the filtering

New HelpDocs articles

None at this time.

REST API/Web services updates

None at this time.

SOAP API / Webservice updates

None at this time.

Endpoints being deprecated and removed

No endpoints currently deprecated and planned for removal.

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