Version 0217

Updated by Victor Jespersen

Release date August 6, 2025

Release summary

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

Quinyx web app Version 0217

Important notice!

We’re excited to announce that Schedule compliance is now live for all customers and is the default schedule validation feature on the web portal!

Please note! Currently, validations from Schedule compliance only apply to schedule actions performed on the web portal. Mobile and API actions are currently not supported with this feature. Read more below.

New functionality

  • Managing group chats just got easier! In this release, we’re introducing the ability for Messenger group admins to assign admin rights to other members.
  • We are introducing a new sorting enhancement in the Schedule/Base schedule view that improves scheduling workflows by allowing managers to sort employees by a unified metric called “Reference hours.”
  • You can now set a custom maximum number of breaks per shift directly in the rule configuration.
  • In this release, we are introducing Unit rule sets. These rule sets allow you to configure rules that should apply based on where a shift is scheduled instead of what agreement template is assigned to them.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • With release 0217, we're introducing a set of enhancements to the filter panel. These changes are part of a larger initiative to support filter sharing across the organization, while also improving clarity and usability based on your feedback.
  • With this release, we've made a small but valuable improvement to the shift offering functionality. Previously, shifts could only be offered if they were scheduled for future dates. Now, managers can offer shifts scheduled for the same day, even if the shift starts later that day.

Bug fixes

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

Employee Hub Version 0217

New functionality

  • We’re making stories even more interactive! In this release, we’ve added the ability to react to comments in stories – helping users show appreciation and engagement with just a tap.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

SOAP API / Webservice updates

  • To support our enterprise customers, we will be releasing a new REST API as an improvement for tag categories querying in version 0217.
  • We will keep the old and new API running in parallel for a set deprecation window (3/4 months/ End of the year 2025).

Important notice!

We’re excited to announce that Schedule compliance is now live for all customers and is the default schedule validation feature on the web portal!

Schedule compliance helps you customize how schedules are validated by enabling:

  • Warnings and hard stops to guide your managers during scheduling.
  • Flexible control over which rules are active, how they’re handled, or even introducing entirely new rule sets tailored to your needs.
Currently, Schedule compliance validations are only enforced for scheduling actions performed 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.

To help you get started, we’ve added helpful articles on HelpDocs:

Explore these to tailor schedule compliance to your organization’s needs.

Interested in learning more? Take a tour!

Quinyx web app Version 0217

Release date August 6, 2025

New functionality

New in Messenger: Share admin rights in group chats

Managing group chats just got easier! In this release, we’re introducing the ability for Messenger group admins to assign admin rights to other members.

 What’s new:

  • As a group admin, you can now grant admin rights to one or more members of your Messenger group.
    • To activate this, you need to check “enable other admins.” After this, you can start assigning admin rights to other members of the chat group
  • This makes it easier to share the responsibility of managing group settings, members, and content.
  • The maximum number of admins for 1 group chat is 100.

Who can use this?

  • This feature is available to all users who have created a Messenger group.

Now, managing group chats is more flexible and collaborative – perfect for teams who want to stay organized and share responsibilities!

Sort employees by reference hours

We are introducing a new sorting enhancement in the schedule/base schedule view that improves scheduling workflows by allowing managers to sort employees by a unified metric called “Reference hours.” This option supports dynamic sorting based on the selected metric within the employee metrics section.

What is new?

  • New sorting option:
    • A new option named “Reference hours” has been added to the display options dropdown in both schedule and base Schedule views.
    • “Reference hours” will adapt to the second metric selected (e.g., nominal, scheduled, or rolled out hours) and sort employees accordingly.
  • Sorting Behavior:
    • Sorting can be ascending or descending.
    • Sorting is always based on the currently selected metric, not fixed to only one.
    • When two employees have the same total hours, sorting will fall back to alphabetical order.
    • If no valid metric is available (e.g., no active agreements), employees will appear at the bottom (0 hours).
    • If the employee has multiple valid agreements, sorting will be based on the summary of hours from all valid agreements.
  • Example:
    • If you want to sort employees based on nominal hours from their agreements, you can now do so by selecting:
      • Sorting: Reference hours
      • Employee metric:
        • Schedule / nominal hours
        • Worked / nominal hours
        • Expected / nominal hours
      All three metrics use nominal hours as the reference and will apply the desired sorting behavior.

What are the benefits of this improvement?

  • Enables scheduling managers to prioritize full-time over part-time employees using nominal hours as a reference.
  • Enhances flexibility by supporting sorting across different hour types.
Schedule compliance rule update: Max breaks per shift rule

You can now set a custom maximum number of breaks per shift directly in the rule configuration. Previously, this rule relied on unit settings, but with this update, you have the flexibility to define a custom value that applies to all employees affected by the rule set.

This enhancement provides more control over break management and ensures compliance with your organization’s specific requirements.

Unit rule sets for Schedule compliance

With this release, we are introducing Unit rule sets. These rule sets allow you to configure rules that should apply based on where a shift is scheduled instead of what agreement template is assigned to them.

To create a unit rule set, you go to Schedule compliance settings under account settings and click add new > Unit rule set. In the rule set settings, you can select or deselect units for which the rules in the rule set should apply.

Rules from both the agreement template and the unit rule sets apply when scheduling an employee who has an applied agreement template and is scheduled on an applied unit.

Why is this important?

Some legal scheduling requirements come from the location itself, rather than from the type of agreement an employee has. This addition allows you to define what location-specific rules are and ensure they are followed.

Read more on unit rule sets in this article about rule sets!

New functionality requiring configuration updates

None at this time.

Updates and performance improvements

Filter panel improvements

With this release, we're introducing a set of enhancements to the filter panel. These changes are part of a larger initiative to support filter sharing across the organization, while also improving clarity and usability based on your feedback.

What is Changed:

Before

After

Panel title: Filter.

Panel title: Adjust view.

Section title: Adjust view.

Section title: Filters.

Saved views.

My views.

Reset icon (❌).

Clear all links.

Delete icon (🗑️) next to each view.

The delete option moved to the three-dot menu.

Side-by-side comparison:

Previous View

Updated View

We will continue adding more changes to this view in the upcoming releases.

Shift offer enhancement

With this release, we've made a small but valuable improvement to the shift offering functionality. Previously, shifts could only be offered if they were scheduled for future dates. Now, managers can offer shifts scheduled for the same day, even if the shift starts later that day.

This enhancement provides greater flexibility in situations like unexpected absences, call-outs, or when additional shifts need to be quickly reassigned during the day.

Bug fixes

  • Resolved an issue where users received the Shift length does not fulfil the minimum duration warning if the connected task had Count as scheduled hours unticked.
  • Resolved an issue where Bank Holidays reduced nominal hours in units where they should not have applied.
  • Resolved an issue where Special Hours were not included in Min/Max rules when using the include opening hours settings.

New Quinyx HelpDocs content

Employee Hub web app Version 0217

Release date August 6, 2025

New functionality

New in stories: React to comments

We’re making stories even more interactive! In this release, we’ve added the ability to react to comments in stories – helping users show appreciation and engagement with just a tap.

What’s new:

  • You can now react to any comment in a story with a heart – just like you can with the story itself.
  • Reactions are a simple way to show support, agreement, or acknowledgment without writing a reply.
  • All users can react to comments they have permission to view.

This update makes conversation in stories more dynamic, encouraging quick and easy interaction across your organization.

Updates and performance improvements

None at this time.

Bug fixes

None at this time.

New Employee Hub HelpDocs content

SOAP API / Web service updates

Introducing pagination with the new REST API for Tag categories

To support our enterprise customers, we will be releasing a new REST API as an improvement for tag categories querying in version 0217.

Currently, we offer the API GET /categories/{categoryExternalId}/tags, which allows our customers to retrieve tags using externalCategoryId.

The current design for this endpoint was producing several 504 (Gateway timeout) responses, and in some instances, our customers reported seeing log traces showing OutOfMemoryError. This was due to the fact that we did not limit the number of tags returned in the integration.

To correct this issue, we are introducing a new API GET /v2/categories/{categoryExternalId}/tags with pagination, as it is essential for performance, efficiency, and usability—especially when dealing with large databases or datasets like our tag service.

Links to the existing and new API endpoint documentation

The old endpoint: GET /categories/{categoryExternalId}/tags

The new endpoint: GET/v2/categories/{categoryExternalId}/tags

As part of our release strategy, we will keep the old and new API running in parallel (dual run), for a set deprecation period (3/4 months/ End of the year 2025).

During this period, we will monitor the new API usage to better track which customers have switched and which are still on the old API.

The current API with no pagination (GET /categories/{categoryExternalId}/tags)will be deprecated with release 226 scheduled for December 10th 2025, our last release of the year. A deprecation warning will also be set in our Swagger documentation as a reminder of this for our Tag integration users.

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?