Version 0123

Updated 8 months ago by Leigh Hutchens

Release date December 15, 2021

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

  • Improvements for the shift booking notification
    • If a shift that someone tries to book is currently owned by someone else, Quinyx will now display that in the notification panel (already released to production).
  • Improvements for the absence request notification
    • If the absence that is requested only covers part of the day, Quinyx will now display the from and to time of the request in the notification panel (already released to production).
  • Improvements for saved filters
    • If you have access to multiple groups, your filter options will now be stored per group when switching between the groups.
  • Improvements for the Webpunch login URL configuration
    • With this release, we've added support for pagination to help reduce loading time for customers with a large number of configurations setups.

Bug fixes

  • Resolved an issue that caused an absence to be marked as worked hours in Statistics.
  • Resolved an issue that caused the Schedule report to take 24 seconds before returning data.
  • Resolved an issue that caused the wrong shift types to be displayed when hovering over the shift in Schedule view.
  • Resolved an issue that caused an internal server error to be produced when saving an edited agreement template.
  • Resolved an issue that prevented all shift types created on a global level in the organization from displaying in the shift types list when creating an absence schedule.
  • Resolved an issue that caused inconsistent API responses for getAgreementTemplatesV2.
  • Resolved an issue that caused an internal server error to be generated while updating the Salary type rule in a Shift type.
  • Resolved an issue that prevented a custom date range from being displayed in Schedule view and produced an internal server error.

New HelpDocs articles

REST API/Web services updates

None at this time.

SOAP API / Webservice updates

None at this time.

Endpoints being deprecated and removed

The following SOAP API endpoints will be discontinued and removed from Quinyx WFM November 2021. They are currently not in use and are not relevant for current version of Quinyx WFM.

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