Version 0208
Updated
by
Victor Jespersen
Release date April 2, 2025
Release summary
Short on time and want a high-level summary? 🚀 Quinyx web app Version 0208 New functionality
New functionality requiring configuration updates
Updates and performance improvements
Bug fixes
Employee Hub Version 0208 New functionality
Updates and performance improvements
Bug fixes
SOAP API / Webservice updates
|
Important announcements
Reminder: Daylight Saving Time has begun - ensure your Tasks & Stories stay on schedule!
DST took effect in North America on Sunday, March 9th. Clocks were moved forward an hour at 2 AM local standard time, meaning that at 2 AM that evening, the clocks read 3 AM local daylight time. However, in most of Europe, DST will not take effect until March 30th.
Daylight Saving Time adjustment - March 9th
At this time, any tasks or stories that you had scheduled to send in Quinyx Employee Hub (Frontline Portal) would have had their send time and due time automatically adjusted. This included recurring tasks.
For example, a task that was scheduled to be sent at 9 AM would have been sent at 10 AM.
If you wanted tasks/stories to continue to have the same send/due times following the March 9th DST change, we recommended that you update the tasks/stories within the scheduled collections prior to them being sent on March 9th. If the task was part of a series of recurring tasks, the task should have been updated after the previous recurrence of that task.
For example, if you wanted a task to continue to send at 9 AM, then you should have edited the send time to 8 AM prior to March 9th. When the DST change came, the send time would have been updated to 9 AM.
Daylight Saving Time adjustment - March 30th
On March 30th, DST will take effect in most of Europe, and clocks will move forward one hour at 2 AM local standard time in Quinyx Employee Hub (Frontline Portal).
Suppose you previously modified any scheduled tasks or stories before March 9th to maintain consistency in send times. In that case, you will need to adjust them back to their original times on/before the European DST change on March 30th.
For example, if the task was initially scheduled at 9 AM and then adjusted to send at 8 AM before March 9th to account for the U.S. DST shift, it will now be sent at 8 AM after the European DST change. It means the time would have to be changed back to 9 AM.
Steps to revert changes made on March 9th
- Identify tasks/stories that had their send times adjusted before March 9th.
- Update the send times to their original intended times before March 9th.
- For example, if the task send time was changed to 8 AM before March 9th, it should now be set back to 9 AM.
- Ensure that any recurring tasks reflect the correct time moving forward.
Now, tasks and stories will return to their correct scheduling.
Renaming Frontline Portal to Employee Hub
We are renaming Frontline Portal to Employee Hub, a name that better reflects its role as a central space for tasks, content, and communications. We will also complete the rollout of our fresh, modernized user interface. This interface is designed to improve usability while maintaining all the features you know and rely on.
What’s Changing?
- A new name: The transition to Employee Hub aligns with how many customers already refer to the platform as their go-to place for workforce engagement.
- An enhanced look and feel: We’ve rolled out a new design with updates to navigation, dashboards, and views that make it easier to find what you need. Please find further information on phase 4 of the redesign in this release note.
What You Need to Know
- The name change will appear on the platform and across our website.
- Our standalone mobile app will now appear as Quinyx Employee Hub in the app stores.
- You don’t need to take any action—your access, data, and workflows will remain the same.
- Employee Hub, like Frontline Portal, still contains the same functionality, namely Tasks, Stories, Files & Folders, Forms, Events and Links
- There will be no immediate change to URLs - work to update URLs will be done in the future, and we will be sure to give ample warning of any upcoming changes.
- Employee Hub will remain in English for all languages, i.e., it will not be translated, with the exception of German.
Quinyx web app Version 0208
Release date April 2, 2025
New functionality
- None at this time.
New functionality requiring configuration updates
Enhanced Compliance Control – Now in Open Beta
What’s New?
We’re introducing a major enhancement to Schedule Validation 2.0 – the Schedule Compliance Rules Page is now available as an open beta, giving administrators full control over how compliance rules are enforced within the scheduling.
With this update, administrators can customize compliance validation rules, set different severity levels (Hard Stops or Warnings), and assign them to specific agreement templates. This ensures that scheduling managers operate within the proper legal and organizational framework while maintaining flexibility where needed.
Why Did We Add This?
Previously, schedule validation was applied based on predefined system logic, limiting customization. Customers needed greater flexibility and control over which rules are enforced, when they apply, and how strict they should be.
By introducing the Schedule Compliance Rules Page, we’re empowering administrators to tailor validation settings to their specific needs—helping organizations maintain compliance while improving efficiency.
How to Use It
Access the Schedule Compliance Rules page through Account Settings. Create or edit rule sets, assign agreement templates, choose the rules that should apply, and define each rule’s severity as either a hard stop or a warning. Once saved, the rules automatically apply to scheduling. Full setup details are available in the HelpDocs.
This update helps organizations stay compliant while reducing manual oversight. It improves scheduling accuracy, prevents errors, and gives administrators the flexibility to enforce policies as needed.
Open Beta Rollout Plan
This feature is being gradually rolled out according to the following plan:
- PHASE 1
- April 7: 20 tenants - discovery & closed beta tenants
- April 14: 40 tenants - discovery & closed beta tenants
- PHASE 2
- April 21: Netherlands, Poland
- April 28: United Kingdom, France
- May 5: Finland, Belgium, Portugal
- May 12: Sweden, Switzerland
- May 19: All remaining countries
For instructions on how to turn on and configure the module, visit our HelpDocs or contact support for assistance.
Updates and performance improvements
Better shift type identification for Optimal headcount configuration
What’s New: We’ve updated the local shift type selection process in the Optimal headcount configuration. Now, each local shift type displays the corresponding unit name alongside its own name.
At the same time, the interface for configuring the Optimal Headcount has been upgraded to use new QUI components.
Why This Update: Previously, users could only see the names of local shift types, making it difficult to differentiate between shift types belonging to different units. This often led to confusion, especially when multiple units had local shift types with identical names.
How to Use: When configuring Optimal Headcount, navigate to the Shift type dropdown. You’ll now see the unit name next to each local shift type, helping you quickly identify the correct option.
Customer Value: This enhancement simplifies the configuration process, reduces errors, and saves time, making it easier for everyone with access to optimization settings to manage headcount accurately.
Introducing Preconditions for Time Tracker Accruals
We’re excited to introduce a new enhancement to Time Tracker Accruals, giving you more flexibility in defining when accruals should begin.
What’s New?
You can now set a precondition before time accruals start for the following accrual drivers:
- Years since start of employment
- Each year after a specified date in the agreement
- Years since birth (age)
How does it work?
When configuring Time Tracker (TT) associations in the Agreement Template, you will now see an option to define a precondition before the accrual driver begins counting.
- Users can specify a time delay by entering a number and selecting months, days, or years as the unit. In this case, when both the preconditions and Time Tracker (TT) association rules are met, the TT will start counting.The reference date for the precondition check is 'employment start date.'
- If no precondition is selected, the default behavior of the chosen accrual driver will work (as described in the accrual drivers section).
For example, if an employee is entitled to vacation after completing three months of employment, you can now set a pre-condition to check this before the vacation time tracker accrual starts.
Visit Time Trackers, practical examples to see how to configure such use cases.
Transparent Error Reporting for Auto Schedule & Auto Assign
What’s New: We've enhanced our Auto Schedule and Auto Assign algorithms by surfacing error messages directly to users. If an algorithm encounters an issue, you’ll be able to see what the error message is about.
Why This Update: Previously, users couldn’t see what went wrong when errors occurred. This often led to repeated attempts without understanding the issue. Now, by displaying the error details, we help users troubleshoot faster and reduce unnecessary retries.
How to Use: After running an algorithm, any indication of an error will now be visible on both the Auto Schedule and Auto Assign pages. Simply navigate to the run panel on the respective page to view the detailed error message.
Customer Value: This update empowers users to quickly diagnose and resolve issues, leading to improved workflow efficiency and less downtime. Users can now take proactive measures to address algorithm errors and enhance their scheduling accuracy.
Updated logic for minimum free days
With the beta version of Schedule Validation 2.0 (described higher up in the release notes), the field Free days in a user's agreement will receive a slight adjustment. Previously, a value of 0 meant the user was still obliged to have at least one free day after working X days in a row. With the update, a value of 0 will mean that the user is no longer required to have any free days.
Redesign of Display Options with one additional sorting option
This update focuses on improving the readability and user experience when configuring different display options in the Schedule and Base schedule view. Additionally, we are adding a new sorting option where you can view employees now sorted by their Last name.
Field Display Updates:
All previously existing radio buttons have been replaced with dropdown menus for a cleaner and more efficient user interface. The arrow next to the selected sorting option now will allow you to decide if you want to see employees sorted in an ascending or descending way.
Bug fixes
- Resolved an issue where forecast variables that weren't supposed to be displayed in the dashboard were shown anyway.
- Resolved an issue where the Labor graph wouldn't update in real time when changing the schedule.
New Quinyx HelpDocs content
Employee Hub web app Version 0208
Release date April 2, 2025
New functionality
- None at this time.
Updates and performance improvements
Employee Hub redesign phase 4
In this release, we have updated the resource views, event cards in the calendar views, and the daysheet view.
More details about some of the views that we have updated and how:
- Adding a widget (now has a white container with a grey background)
- Saved audience (now has a white container with a grey background)
- Added a grey background to the app, removing card borders (unless a category is set), updated the status badge to a new design to differ from the tags, and colors have been updated to be more vibrant in some statuses
- We have updated the notifications, file preview, and profile pages, housing updated content inside a white container against the new grey background
- The breakdown view of resources has been updated, mainly its text and the use of a status badge where appropriate, the status color on these items now matches that of the cards in the dashboard views
- The canceled page state has been changed, the page used to have a grey background now we indicate canceled using a status badge
- The view switcher (between calendar and home) on the home page has been changed to use a new toggle button
- Event cards for week, month, and daysheet view have been updated with a new look and new icons
- Update of the daysheet view with a new design with new colors that are very similar to the previous ones, new day separators, and new current day indicator.
Set preferred default sort order
You can now choose to set your own default sort order, rather than having to set the sort order each time you return, for:
- Global searches
- Tasks Hub (per collection) and corresponding local searches
- Files Hub (per collection) and corresponding local searches
- Stories Hub (per collection) and corresponding local searches
- Forms Hub (per collection) and corresponding local searches
Please note:
- Sort settings are set per user i.e. they are individual to you.
- Sort settings are set per hub collection i.e. they can be different for Files Hub ‘All' collection vs ‘Shared by me’ collection etc.
To select your preferred sort order:
- Select the sort button.
- Select your preferred sort option.
- Select the save sort settings button.
Bug fixes
- None at this time.
New Quinyx HelpDocs content
- None at this time.
SOAP API / Web service updates
This is an early announcement that with Version 0211, we will introduce new fields in our SOAP Web Services; specifically, new fields will be added to wsdlUpdateAgreementsV2. These changes are being made in order to enable you to configure different Nominal hours setup using SOAP Web Services. More details will be shared closer to the release date.
Please make sure to forward this information to the party within your company responsible for integrations.
