Version 0111

Updated by Leigh Hutchens

Release date June 30, 2021

Quinyx works relentlessly to strengthen information security and continuously improve measures to protect data. As part of this work, we have updated our Information Security Overview to reflect policies, mechanisms, steering processes, and organizational structure that form our commitment to protecting your data. The updated version can be found side-by side with the current version in the Information Security section on our website and will be valid through agreements 2021-08-16.

New password policy

As of the release of version 0111, all new passwords must:

  • Contain a minimum of 12 characters (128 maximum).
  • Contain at least 2 numeric characters.
  • Contain at least 2 letters.

If a manager resets an employee's password, or if the employee chooses to reset the password, the system will require a new password to be chosen when logging in.

The user account will be blocked after 6 unsuccessful login attempts. A manager must then reactivate the account.

The password must be updated the next time the user resets the password or the manager sets a password for the user.
Current passwords will not be affected. The above applies only to passwords that are changed or reset.

New functionality

Absence settings

We've made improvements to the absence reason list view and full add, edit, delete functionality for absence types, so you now have full configuration support for absence settings.

List of absence reasons, improvements

We've added "Salary type" to the overview list so that you can quickly identify whether there are any salary types associated with a unique absence type.

The option to "Manage absence reason types" has now been moved to under the more ubiquitous "..." button, next to the new "Add absence type" button:

Add, edit, and delete absence types

By clicking "Add absence type", you can now directly add a new absence type in the absence settings. Here you can give the absence a name, define the calculation rules, and access advanced settings. You can also edit or delete any existing absence types:

Updates and performance improvements

  • Previously, it wasn't possible to add an absence if the period you viewed contained a locked schedule date. We've changed this so that you can add an absence outside the locked schedule date, even when viewing a period with a locked schedule date.
  • It's now possible to add a part time absence that contains up to four decimals.
  • When max scheduled hours per day/week is set to zero (0) on an employee's agreement, we now consider that as the warning not being used, and therefore we will not trigger warnings for that when scheduling.
  • We've made a change so that it is not possible to move draggable panels outside of the screen.

Bug fixes

  • Resolved an issue that prevented a manager from seeing their own salary in an agreement.
  • Resolved an issue that caused a time punch occurring in the past to display the timestamp for the current day.
  • Resolved an issue that caused an agreement for a shared employee that was connected to a shift and punch to be invisible in the Time card.
  • Resolved an issue that caused the schedule time multiplier to increase the total number of scheduled hours in the employee metrics, even when the associated unsocial time (UT) salary type being multiplied was removed.
  • Resolved an issue that caused the total number of scheduled hours to be incorrect when the associated UT salary type was removed from the salary output.
  • Resolved an issue that prevented a manager from denying shift requests.
  • Resolved an issue that connected the wrong agreement to a shift when an employee had an agreement with a home unit and an away unit after a manager approved a shift.

New HelpDocs articles

Please note that next week (week 26), we will begin rearranging HelpDocs to more closely align with the way our web app is structured. As you can imagine, this may take a little time, so we thank you in advance for your patience. Our goal is to make it easier to find the documentation you need.

REST API / Web service updates

None at this time.

SOAP API / Web service updates

None at this time.

Endpoints being deprecated and removed

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 Quinyx Forecast or obsolete. Read more about Quinyx Forecast and the improved functionality here and about the new REST APIs here.

6.2 wsdlGetForecasts

6.3 wsdlUpdateForecasts

6.5 wsdlGetMonthlyView

6.6 wsdlUpdateForecastV2

6.8 wsdlUpdateForecastsV3

6.4 wsdlGetSalesData

6.9 wsdlGetSalesDataV2

6.7 wsdlGetOptimalStaffing

4.6 wsdlUpdateAdminGroupRelationships <- not applicable for Quinyx WFM

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?