Version 0242

Updated by Victor Jespersen

Release summary

Release date August 5, 2026

Short on time and want a high-level summary?  🚀

Quinyx web app Version 0242

New functionality

  • Quinyx' optimisation algorithms, Auto Assign and Auto Schedule, are now centralised into one user-friendly view: the Schedule Automation page.

New functionality requiring configuration updates

  • If you operate in Norway, you can now configure your self-certified sick absence limits yourself instead of asking Quinyx to do it for you.
  • Share one day count across multiple absence types! You can now create, manage, and link absence types to custom Day Count Absence Groups.

Updates and performance improvements

  • Improved Absence Management: Access Absence reason types and Day count absence groups seamlessly from the updated three-dot menu on the Absence Types page.

Bug fixes

  • None at this time.

Mobile app

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Employee Hub Version 0242

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

REST API / Web service updates

  • None at this time.

Important information

Introducing the Quinyx Developer Portal

We've launched a dedicated developer portal at developer.quinyx.com, centralizing all integration resources in one place.

The portal includes API reference documentation, step-by-step guides, and quick-start resources for both SOAP and REST APIs. Documentation is versioned across v1, v2, and v3, so you can reference the docs that match your current implementation.

Next week and in the following weeks, we will start removing the API documentation available on HelpDocs and Swagger UI and redirect users to the new Portal.

Quinyx web app Version 0242

New functionality

Schedule Automation View
Accessible by tenants that either have the Auto Schedule or Auto Assign modules enabled.

Navigation: Schedule > Schedule Automation in the navigation headers.

Quinyx's optimisation algorithms, Auto Assign and Auto Schedule, are now centralised into one user-friendly view: the Schedule Automation page. Previously, Auto Schedule (automatic generation of anonymous shifts) and Auto Assign (automatic assignment of those anonymous shifts to employees) had dedicated pages of their own, meaning you had to move between screens to run both steps of the process. Now you can configure and launch either algorithm from a single place.

What's new

  • One page for both algorithms: Set up and launch Auto Schedule and Auto Assign runs from the same view, instead of switching between separate pages.
  • Improved unit selector: Search directly in the unit tree instead of scrolling, and see organisation and district names with a live counter of how many units you've selected within each.
  • Improved history view: Time filter on the historical runs to increase visibility.
  • Various UI improvements: Aligned UI components with the rest of the Quinyx application.

New functionality requiring configuration updates

Set up Norwegian self-certified sick absence (egenmelding) yourself

If you operate in Norway, you can now configure your self-certified sick absence limits yourself instead of asking Quinyx to do it for you.

Open an absence type in Account settings, go to Advanced settings and tick Special Norwegian self-certified sick absence. Four fields appear, where you set the maximum days in one leave occasion, the maximum number of leave occasions in a rolling period, the length of that period, and the maximum days allowed across it.

The setting is off by default on all existing absence types, so nothing changes until you turn it on.

When your rules change, whether through a legal update, a collective agreement or your own policy, you can now apply it the same day.

Manage day count absence groups in Quinyx

Day count absence groups let several absence types share one day count. You can now create and manage them yourself and link absence types to them.

To create, rename, or delete a group, go to the absence types page in Account settings, open the three dots menu and select Day count absence groups. Each group shows the absence types linked to it. A group cannot be deleted while it is still linked to one. Day count absence groups is located in the top right-hand corner.

To link an absence type, open it in Account settings, go to Advanced settings, tick Link day count absence group and choose the group. Group settings take priority over the absence type's own settings, as before.

This was previously a configuration request handled by Quinyx, so you no longer need to raise a ticket or wait for us.

A superuser or administrator needs to complete this configuration before it takes effect for your employees.

Updates and performance improvements

Clearer menu when managing absence settings

The three dots menu on the absence types page now reads Absence reason types and Day count absence groups, and has been rebuilt to display correctly now that it holds more than one option.

Bug fixes

  • None at this time.

  • New HelpDocs content

  • None at this time.

Mobile apps

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Employee Hub web app Version 0242

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

New HelpDocs content

  • None at this time.

REST API / Web service updates

None at this time.

Please make sure to forward this information to the party within your company responsible for integrations.

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. 

How Did We Do?