Version 0140

Updated by Leigh Hutchens

Release date August 10, 2022

New functionality

None at this time.

Updates and performance improvements

  • As of this release, when you add a task to a shift in Schedule the default time of the task will be the time of the shift. This change has been made due to popular demand up until this release, this is how it's worked in Base schedule but not Schedule.
  • Starting with this release, the option of including the variable "Forecast cost" in the Punched hours,  Schedule cost as well the Time cost reports are removed. The reason for this is that that variable was part of our legacy forecast module which is no longer in use.

Bug fixes

  • Resolved an issue that caused the Punch missing warning to disappear when filtering on Type or Section under Tasks.

Training material

Don't forget to watch the training videos that are available in HelpDocs! The videos cover:

  • Configuration & Settings
  • Schedule & Time Management
Click here to view Quinyx WFM training videos.

New HelpDocs articles

SOAP API / Webservice updates

New validations for wsdlUpdateEmployees

When creating or updating an employee through the SOAP API, validation is added for non supported characters in the following places : givenName, familyName, staffCat, address1, address2, zip, city, country, locale, loginId, cardNo, info, legalGuardianName.

If you try to update one or more of these settings including characters   [(\|\]\/~+@!%^&*={};:?><')] you will receive a validation error.

For the phoneNo, cellPhone, nextPhone only possible characters are space numbers 0-9, dot ., plus +, dashes - and /

Endpoints being deprecated and removed

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