Version 0110

Updated by Leigh Hutchens

Release date June 16, 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 2 months from today.
In regards to the above message, Quinyx will change the current password policy in the release of version 0111, planned for 30/6. The current policy can be found here. The current standard password policy will be removed, and the new standard will be replaced with a modified high version.

New password policy level 30/6 will require that all passwords will need to:

  • Contain a minimum of 12 characters long (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 that you choose a new password 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


Add/Edit absence

In this release, we've made some improvements so that it is not possible to create an absence with a duration longer than 12 months.

When adding or editing an absence, you'll now see that the dates beyond 12 months are greyed out, and it is not possible to select them. A text is displayed explaining why you can't select those dates when you hover over them:


In this release, we've combined all of the information from the Variable Settings, Input Data, and Forecast Configuration areas within Quinyx' GUI into one area called "Variable Settings" for easier management.

You can read more about that here.

Updates and performance improvements

Statutory / Non -statutory balances as per defined dates

We've added the possibility to view statutory and non-statutory vacation hours as per the day before they expire. This functionality is connected to Time Trackers that are set to "first to expire" AND have the view balance as per "month / day".

When those conditions are met, the statutory and non-statutory balances are shown as per the following dates:

Statutory hours current year (2021) - Show as per 2022-06-30 (current year+1 : June 30)

Non - Statutory hours (2021) - Show as per 2026-12-31 (current year +5 years : December 31)

Statutory hours year - 1 (2020) - Show as per 2021-06-30 (year -1 +1 year : June 30)

Non - Statutory hours (2020) - Show as per 2025-12-31 (year -1 +5 year : December 31)

Non - Statutory hours (2019) - Show as per 2024-12-31 (year -2 +5 year : December 31)

Non - Statutory hours (2018) - Show as per 2023-12-31 (year -3 +5 year : December 31)

Non - Statutory hours (2017) - Show as per 2022-12-31 (year -4 +5 year : December 31)

Non - Statutory hours (2016) - Show as per 2021-12-31 (year -5 +5 year : December 31)

From a user perspective, this means that the next occurrence of chosen dates will not be taken into consideration at all. So all periodized Time Trackers set first to expire AND show balance as per month/day will have the same hard coded dates. Read more about the "Dutch vacations" here.

Agreement changes on shift

When an agreement is changed on a shift, the selected agreement will now also be inherited to the connected punch.

Bug fixes

  • Resolved an issue with additional absences on the same day in combination with long-term absence of the same type created an extra "karensdag".
  • Resolved an issue that caused missing access control on update password functionality.
  • Resolved an issue that prevented a unit from being saved if a manager who was assigned to that unit and later had the manager role removed.
  • Resolved an issue that allowed managers to approve their own punches even when “Allow attest of own punches” was unticked.
  • Resolved an issue that displayed an absence longer than three months in the schedule but not on the Time card.
  • Resolved a 400 error when a manager role was removed from an employee after being assigned to a Unit.
  • Resolved an issue that prevented Unit integration keys from being entered.
  • Resolved an issue with shifts over daybreak that caused employees using base schedule as overtime to erroneously receive overtime for all shifts when shifts exceeding midnight had been rolled out on the last day of rolled out period.
  • Resolved a Schedule view issue that caused absence/shifts to not display as unavailability on section level when Monthly view was selected.
  • Resolved an issue with group management that prevented an integration key for a unit from being saved.
  • Resolved an issue that prevented an absence shift to be reassigned if the absence took place over a long period of time.
  • Resolved an issue where the worked/nominal employee metric incorrectly considered absence shifts' "Count as scheduled hours" setting, which caused issues when attempting to analyze why employees receive overtime compensation. Now, that same metric instead looks to absence shifts' "Count as worked hours" setting.
  • Resolved an issue with duplicate skill categories returned from wsdlGetSkillCategories
  • Resolved an issue with time zones in Webpunch with unplanned punches.

New HelpDocs articles

Please note that in the coming weeks we will be rearranging HelpDocs to more closely align with the way our web app is structured. Our goal is to make it easier for you to find the documentation you need. Stay tuned!

REST API / Web service updates

None at this time.

SOAP API / Web service updates

WsdlUpdateEmployee : new optional flag added throwExceptionOnHomeUnitEndDate

This is a Boolean flag that is strongly suggested to be set to True. Then you will receive an exception if you are updating roles and the role you are updating is the only existing role on the employees home unit. 

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?