Version 0158

Updated by Leigh Hutchens

Release date April 19, 2023

Release summary

Short on time and want a high-level summary?

Web app

New functionality

  • None at this time.

Updates and performance improvements

  • A warning will appear when the opening time of one day is before the closing time of the previous day. This check is only applied within the same configuration, not across multiple configurations.

SOAP API / Webservice updates

  • No updates in this release.

Bug fixes

  • You might be interested in one of our bug fixes in this release. If you want more information, click here.

New functionality

None at this time.

Updates and performance improvements

Warning when attempting to add overlapping opening hours

We've added an additional warning when a user tries to add overlapping opening hours in the same configuration. Now, a warning will appear when the opening time of one day is before the closing time of the previous day. This check is only applied within the same configuration, not across multiple configurations.

Bug fixes

  • Resolved an issue that produced an internal server error when trying to change the date for an existing absence.
  • Resolved an issue that caused a new, identical shift to be created and assigned as a productive shift when punching in and out with a leave reason in Webpunch or the mobile app.
  • Resolved an issue where One-time passwords were possible to be reused when setting the new password.

New HelpDocs articles

Reminder! If you would like to receive bi-weekly email notifications about new releases, you can sign up here.

SOAP API / Webservice updates

No updates in this release.

No endpoints are 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 of our customers to make use of our APIs to maintain data and to make sure that information is up-to-date. To ensure the scalability of our APIs while growing our customer and user base, we've decided to add restrictions on the usage of our SOAP APIs. These restrictions will be enforced programmatically, which means 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 coming 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?