Version 0219

Updated by Leigh Hutchens

Release date September 3, 2025

Release summary

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

Quinyx web app Version 0219

New functionality

  • We’ve made it easier to plan for roles that span different shifts. You can now select multiple shift types when setting up Optimal Headcount and Labor Standards. Have the headcount calculated across all chosen shifts together, giving you a more realistic view of staffing needs.
  • You can now import daily Productivity Targets via API and view them directly on the Schedule Page next to the Productivity KPI.
  • We’ve made it possible to create, edit, and delete Labor Standards via API, making updates faster and scalable.
  • We have simplified compliance with new rule types for employees' days off.
  • The audit log entries will cover the creation and changes of these objects. When you remove a role assignment to an employee, it will be presented as a change where the end date is set to the current date.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • This release brings continued improvements to the Filters panel to enhance readability and usability.
  • We have added support for simultaneously logging out from an Identity provider (IDP) like Azure, Google or Okta, when the user is logging out from Quinyx.

Bug fixes

  • You might be interested in a bug fix in this release. For more information, click here.

Employee Hub Version 0219

New functionality

  • None at this time.

Updates and performance improvements

  • We have made an improvement in the viewing of the file details. From now on, when you go into the file's preview view, the details of that file will be collapsed by default, giving more room for the picture above as a default.

Bug fixes

  • You might be interested in a bug fix in this release. For more information, click here.

SOAP API / Webservice updates

  • None at this time.

Important notice!

Please note! Schedule compliance validations are enforced across web, mobile, and APIs. However, creating, updating, and validating the new 2.0 validation rules is currently only supported through the web portal. The mobile app and API still rely on the old validation engine, which does not support newly added or updated rules. As a result, any changes to Schedule compliance rules—whether additions, updates, or archival—will only take effect when scheduling through the web portal. These rules will not be validated when scheduling via the mobile app or API.
In the first version of the Schedule Compliance, we introduced one standard rule set (called the Default rule set) that was applied to all Agreement Templates. But, as soon as the users would create their own custom rule set, and link an Agreement Template to it, then the system would not pick up the standard configuration (default rule set) from the Agreement templates, but only look at what was manually added as rules.

We realized this was not a very intuitive approach, and could lead to users configuring new rules without understanding that they would be losing all “default” rules that would normally be checked against the agreement template.

Logic from 2025-08-12: We released an improvement that adds the standard configuration to newly created Schedule compliance rule sets.

Now, when a user creates their own custom Schedule compliance rule set and links an agreement template to it, then the system will pick the standard configuration from the default rule set automatically.

Note that this improvement is, however, not applied to customers who already created new rule sets before 2025-08-12.

Quinyx web app Version 0219

Release date September 3, 2025

New functionality

Configure multiple shift types in Optimal headcount

We’ve made it easier to plan for roles that span different shifts. You can now:

  • Select multiple shift types when setting up optimal headcount and labour standards.
  • Have the headcount calculated across all chosen shifts together, giving you a more realistic view of staffing needs.

This means you no longer need to create separate configurations for each shift type. For example, an employee can cover opening, morning, and afternoon shifts all within the same headcount setup.

This update also prepares the ground for smoother auto schedule configuration in Quinyx.

Import and view productivity targets

You can now import daily productivity targets via API and view them directly on the schedule page next to the productivity KPI.

To define your targets in your external system, specify:

  • The units or sections the targets apply to.
  • Whether the target is to reach an exact value, stay below, stay above, or be between two values.
  • The actual target daily value.
  • The period the target applies to (the same daily value can be applied to a longer period than a single day).

In Quinyx, first go to the productivity KPI and choose to create targets for it. Then, set the External ID to enable the integration. Last, push the data using our public endpoint. Endpoint details are explained here: Swagger UI.

Once the data is imported, scheduling managers will see productivity targets on the schedule page, alongside the productivity KPI, with clear indicators showing whether targets are being met.

Manage labor standards via API

We’ve made it possible to create, edit, and delete labor standards via API, making updates faster and scalable.

To enable this, simply configure an External ID on your optimal headcount record — this serves as the link that allows API integration. The External ID should be max 160 characters long, and no special characters or spaces are supported.

Once the External ID is configured, the labor standards can be pushed using our public endpoint. Endpoint details are explained here: Swagger UI.

Labor standards that are pushed to Quinyx via API will be visible in the interface, in the same way as those configured manually.

This update gives operations and integration teams the flexibility to either manage labor Standards manually in Quinyx, or maintain them in an external system and automatically push updates into Quinyx through the API.

New schedule compliance rule types: Days off per week or month

We have simplified compliance with new rule types for employees' days off.

Weekends off per period (weeks or month)

Ensure employees have a minimum number of weekends off. You can specify the number of free weekends over a variable number of weeks or per calendar month.

Split days off per week

This rule guarantees that employees receive several full days off each week. The resting days in the week do not need to be consecutive.

Consecutive days off per weeks

This rule ensures that employees have a consecutive period of days off across several weeks. You can configure both the number of days and weeks.

The Danish hospitality sector exemplifies the need for these rule types to ensure employees receive their required days off. Learn more about these rules at schedule compliance rules article.

Role assignments, role creation and level changes are coming to audit logs

New objects will be covered in the audit logs: 

  • Employee role assignments 
  • Role 
  • Rank (levels)

The audit log entries will cover the creation and changes of these objects. When you remove a role assignment to an employee, it will be presented as a change where the end date is set to the current date.

New functionality requiring configuration updates

None at this time.

Updates and performance improvements

Filters panel improvements

This release brings continued improvements to the Filters panel to enhance readability and usability.

Filters panel updates

  • Collapsed sections by default: The filters panel is now cleaner and less overwhelming, making it easier to find what you need.
  • Persistent section preferences: Open the sections you use most often, and they will stay open every time you access the panel, helping you work faster and more efficiently.
SSO providers - Log out from IDP support

We've added support for simultaneously logging out from an Identity provider (IDP) like Azure, Google, or Okta when the user is logging out from Quinyx. We have added settings for this into both our SSO-providers: SAML and OpenID.

Currently, the SAML provider only supports logout for Microsoft Azure/Entra ID. 

Salary files - SFTP settings

The SFTP settings for salary files are now available in Account settings for users with Level 1 access. You also need to have access rights for SFTP Settings.

This configuration is used to define the customers sFTP setting for their payroll transfer.

The password is masked to increase the security.

Bug fixes

  • Resolved an issue that caused the employee sort order to display incorrectly when using Additional fields in the schedule. After adding a shift, the sort order would break until the page was refreshed. It now updates correctly in real time.
  • Resolved a rounding issue in the "Date and time" part of the shift to display with excessive decimal places.
  • Resolved an issue in Optimal Headcount and Labor Standards where a space was missing between the arrow icon and the text "Add new optimal headcount".
  • Resolved an issue where the Min/Max optimal headcount wasn't visible in the schedule statistics.
  • Resolved an issue where the Auto Schedule and Auto Assign modules' landing page didn't display the runs correctly.

New Quinyx HelpDocs content

  • None at this time.

Employee Hub web app Version 0219

Release date September 3, 2025

New functionality

None at this time.

Updates and performance improvements

We've made an improvement in the viewing of the file details. From now on, when you go into the file's preview view, the details of that file will be collapsed by default, giving more room for the picture above as a default.

Bug fixes

  • Resolved an issue where the Due date field wasn't populated when viewing the task overview in the List view.
  • Resolved an issue where you could select multiple MCQ options on tasks when you unassigned or restarted tasks.

New Employee Hub HelpDocs content

None at this time.

  • SOAP API / Web service updates

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?