Version 0187

Updated by Leigh Hutchens

Release date May 29, 2024

Release summary

Short on time and want a high-level summary?

Quinyx web app Version 0187

New functionality

  • You can now access standard variable data through the APIs for specific units, specific variables, and specific periods of time.
  • We're releasing static rules across hours, days, and weekdays.

Updates and performance improvements

  • Quinyx has successfully removed support for the old SSO configuration (Classic and Mobile) in 2024. In the next mobile release, the ability to search for and find old mobile SSO environments under the “Settings” tab in the mobile apps login page will also be removed.
  • We've extended the functionality of the following accrual drivers by adding a new parameter (checkbox) to deduct on bank holidays.

Bug fixes

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

Frontline Portal Version 0187

New functionality

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

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

SOAP API / Webservice updates

  • Check out the updates and new documentation here.

Quinyx web app Version 0187

Release date May 29, 2024

New functionality

API access for standard variables

We've been working on enabling standard variable data through our APIs. You can now access standard variable data through the APIs for specific units, specific variables, and specific periods of time.

Static rules across hours, days, and weekdays

We're releasing static rules across hours, days, and weekdays. You can now use these static rules for a specific optimal headcount. For example, as a user with write access to Optimization settings, I can set up optimal headcount variables, and labor standards using static rules within a specific period.

New functionality requiring configuration updates

No updates at this time.

Updates and performance improvements

End of life of the old mobile SSO

Quinyx decided that the support for the old SSO configuration (Classic and Mobile) would be removed during 2024 and has been successfully removed a while back. In the next mobile release, we will also remove the support to search for and find the old mobile SSO environments under the “Settings” tab in the mobile apps login page. We urge all our customers and users to start using the new SSO login flow, which allows you to type in your user name immediately instead of searching for the environment. You can find information about how users log in with the mobile apps with the new SSO configuration here.

New configurations are already available in the Manager Portal, and you'll now only need one configuration for all Quinyx applications. We recommend that customers still using the old configuration start planning to set up the new configuration. 

The new configuration provider setup supports either SAML 2 or OPEN ID standards.

Accurate Deductions of Absences on Bank Holidays

Why the improvement?

To enable Time Tracker deductions of absences during bank holidays. Previously, when a shift was scheduled on a bank holiday and an employee applied for an absence, the absence was not automatically deducted from the relevant time tracker balance. This caused vacation, flex time, and compensation Time Tracker balance discrepancies.

What have we done?

To address this issue, we have extended the functionality of the following accrual drivers by adding a new parameter (checkbox) to deduct on bank holidays.

Here’s how you can set it up:

  1. Create Time Tracker Association: In the agreement template, create a Time Tracker association with one of the following accrual drivers:
    • Each vacation leave day.
    • Each vacation leave hour.
    • Each absence type leave day.
    • Each absence type leave hour.
  2. Enable Deduct on Bank Holiday Option:
    • When the Deduct on bank holiday checkbox is enabled in the time tracker association, the absence(s) will create a transaction for the chosen time tracker.
    • If the Deduct on bank holiday checkbox is disabled, the absence will not create a transaction for the chosen time tracker.

Additional Configuration Requirements:

  • The Deduct on bank holidays checkbox will only appear if the Adjust balance based on absence shifts radio button is selected.
  • For this option to function correctly, ensure the Only count scheduled day option is enabled on the absence type connected to the accrual driver.

This improvement will ensure that absences on bank holidays are accurately deducted from the relevant time tracker balance. 

Bug fixes

  • Resolved an issue regarding warnings in the base schedule stating no valid agreement on the unassigned shifts despite no unassigned shifts in the base schedule.
  • Resolved an issue regarding bank holiday configuration: Create leave on daybreak if missing punch, not creating absences.
  • Resolved an issue regarding KPIs for employees not being visible in the employee metrics for certain months.
  • Resolved an issue regarding users not being able to zoom in on images in Messenger.

New Quinyx HelpDocs content

HelpDocs articles

Frontline Portal Version 0187

Release date May 29, 2024

New functionality

None at this time.

Updates and performance improvements

None at this time.

Bug fixes

  • None at this time.

New Frontline Portal HelpDocs content

HelpDocs articles
  • None at this time.

SOAP API / Webservice updates

  • As part of our long-term attempt to move away from SOAP APIs to REST APIs, we’re releasing the following absence-related REST APIs as of this release:
  • Our tentative plan is to release additional absence-related APIs - PUT Absence, Delete Absence - in the coming sprints.
  • Like mentioned before, various absence-related SOAP APIs will be deprecated with time as a result of the above-mentioned REST APIs. In due time, we will communicate a deprecation timeline to affected parties.
Important! Some of you have expressed concern regarding what the timeline will look like. Please rest assured that the timeline in question will reflect the capacity of the affected parties to plan and resource the needed migration.
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?