Version 374

Updated 2 months ago by Leigh Hutchens

Release date May 6, 2020

Important information regarding Integrations

We encourage all our customers to make use of our APIs to maintain data and to ensure 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 APIs. These restrictions will be enforced programmatically. We are currently monitoring usage of our APIs to identify which restrictions will be necessary to ensure performance over time.The first limit will be related to number of concurrent calls which will be set to 5. You should expect response code 429 if you happen to exceed this limit. We will inform you when this limit and any additional limits will be enforced in upcoming release note for you to have time to make any necessary changes to your clients.

Clarification: The limit related to concurrent calls will not be enforced in the release 2020-05-06. We are currently monitoring and will give more detailed information on the date of the change in upcoming release notes. (original information edited 2020-05-05) 

New functionality

Validation for period remuneration

In some markets, Germany for instance, there is an employment type that has a rule that in one month you cannot earn more than €450. This is commonly described as a mini-job and/or minijobbers.

With version 374, we have added additional support for this employment type and now offer the possibility on agreement template level to define a cost period and a cost limit. You will receive a validation warning when scheduling an employee and the estimated cost for the period exceeds the configured value.

The validation is done when scheduling, such as:

  • Adding a shift
    • From Classic or from the mobile app (Neo support is coming)
  • Extending an existing shift
    • From Classic or from the mobile app (Neo support is coming)

The validation is not considering validations when:

  • Rolling out a fixed schedule
  • Rolling out a Base schedule in Neo
  • Adding punches
  • Adding manual salarytypes

Configuration for this is done from Neo - Account settings - Agreements - Templates - selected template - Working hours and periods.

  • Cost period - This is the period that the system will validate against
  • Cost period values - This is the value that the system will validate against

Updates and performance improvements

  • It is now possible to manage an overlapping leave application the same way as you would add an overlapping leave application (Note: this requires that the allow overlapping leave functionality is activated under Settings - Units - functionalities tab)

Bug fixes

  • Correction to leave saved with same start and end date and presenting an error message to the user.
  • Corrections to shift assignment notifications being sent out when schedules have been published and then unpublished.
  • Salary details report now downloads as XML and does not open in a new window.

API / Web service updates

wsdlGetEmployeesV2 : Now returns extGroupId in the response if set

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 to ensure 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 APIs. These restrictions will be enforced programmatically. We are currently monitoring usage of our APIs to identify which restrictions will be necessary to ensure performance over time.The first limit will be related to number of concurrent calls which will be set to 5. You should expect response code 429 if you happen to exceed this limit. We will inform you when this limit and any additional limits will be enforced in upcoming release note for you to have time to make any necessary changes to your clients.


How Did We Do?