Version 0205
Updated
by
Leigh Hutchens
Release date February 19th, 2025
Release summary
Short on time and want a high-level summary? Quinyx web app Version 0205 New functionality
New functionality requiring configuration updates
Updates and performance improvements
Bug fixes
Frontline Portal Version 0205 New functionality
Updates and performance improvements
Bug fixes
SOAP API / Webservice updates
|
Important announcements
Release highlights
To help you get the most out of this release, we'll be creating highlight videos showcasing key updates and new features. Check back next week! 🎉
Quinyx web app Version 0205
Release date February 19th, 2025
New functionality
Manager comments on Shift unassignment requests
Similar to the previous releases for shift swaps and shift bookings, we are now introducing a new feature allowing managers to add comments when handling shift unassignment requests.
What’s New: Managers can now leave a comment in the notifications panel within the manager portal before approving or denying a shift unassignment request. This feature enhances transparency by giving employees clear explanations for manager decisions, particularly when a shift unassignment request is denied.
- The comment will be visible to employees in the Qmail they receive.
- Managers can also view these comments in the shift unassignment audit logs for future reference.
New functionality requiring configuration updates
- None at this time.
Updates and performance improvements
Improved rounding of Optimal Headcount values
Previously, when displaying the hourly data in the labor display group:
- Optimal headcount values would follow the rounding rule set in the labor configuration;
- Scheduled headcount values would not be rounded on an hourly level but averaged.
As a consequence, comparing optimal and scheduled headcounts for a single hour could not be done effectively.
From now on, the rounding logic for hourly values that have been previously applied to the scheduled headcount values will also be applied to the optimal headcount values.
This means that:
- The rounding rule set in the labor configuration only impacts the rounding at the lowest granular level. For example, if the needed headcount is 4.33 from 10:00-10:15 and the rounding method is up, then the optimal headcount for those 15 minutes will be 5.
- There is no rounding applicable to hourly levels (unless that’s the lowest granular level). If the optimal headcount is 1 for the first part of the hour and 2 for the second part, then the optimal headcount will show 1.5. If the hourly level is the lowest granular level and the headcount needed is 4.33 with the rounding method up selected, then the optimal headcount for that hour should be 5.
- There is no rounding on a daily/weekly/monthly level. These values follow the rules that are configured for the optimal headcount variable (values are either summed or averaged, not rounded up).
Improved support for monitoring and editing shared employees' schedule
With this release, we’re continuing to improve the support of our software in allowing manager local managers to monitor and edit shared employees' schedules.
Away-group shift and absence shift hour count
Up until this release, the hour count of current-group shifts, absence shifts, and punches have been displayed in the schedule. As of this release, we’re introducing the same hour count for away-group shifts and away-group absence shifts, respectively:
The purpose of introducing this hour count of away-group items is for those local managers whose direct reports have shifts and/or absences in various locations to be able to more easily monitor the current state of their direct reports' scheduled hours versus their nominal hours. More specifically, it is intended to allow said managers to more efficiently troubleshoot in cases a given direct report’s scheduled hours are misaligned with their nominal ones due to away-group group managers' inadvertence or neglect.
Bug fixes
- Resolved an issue where employees got displayed in the wrong section.
New Quinyx HelpDocs content
Wepunch documentation update
We’re currently in the process of expanding our Webpunch documentation to provide you with more detailed and comprehensive guidance. Stay tuned for upcoming updates as we continue to enhance our resources to better support you. In the meantime, take a look at our new article:
Frontline Portal Version 0205
Release date February 19th, 2025
New functionality
Automated translations
Background: With our function Automated translations in the Frontline portal, we can translate free text field content in Stories/Tasks/Forms so that the users who are the recipients of the Task/Story/Form can see the content in their chosen language in the Frontline Portal. This use case can help customers that:
- Need to share urgent Tasks/Stories/Forms from a central, for example, English-speaking HQ to a user group of employees across numerous geographies speaking several different languages.
- Feels that manual translation of Task/Story/Form is too slow and time-consuming for the required turnaround of the Task/Story/Form, and manual & ad hoc translations take a long time.
Our solution:
As a manager/content creator:
- As a manager who is creating a Task/Story/Form in the Frontline Portal, you can enable automatic translations for a specific Task/Story/Form. Once you have activated Automated translations for the Task/Story/Form, you can choose which languages you want the text in the Task/Story/Form to be translated into. You can choose to translate it into all the languages we support in the Frontline Portal. Once the Task/Story/Form is sent/distributed or updated after being sent/distributed, our AI tool will translate the free text field content into the chosen languages. The fields and functions that can be translated are the following:
- Tasks: Title, description, notes, questions ("Short answer" with a predefined correct answer will not be translated).
- Stories: Title, description.
- Forms: Title, questions.
Any potential responses from the user who receives the task are not supported now.
As a user receiving and reading the Task/Story/Form:
- The user receiving and looking at a Task/Story/Form will see the free text of that Task/Story/Form that has had an automated translation in the language they have chosen in the Frontline Portal or their mobile app. The user also has the possibility to switch between the translated text and the original text.
Redesign of the Frontline Portal - phase 1
In this release, we are happy to announce that we are releasing the first phase of the new design for the Frontline portal that we announced in release notes 0201. Important to note is that we will not be changing any functionality - only the look and feel.
In this release, we have updated the cards for stories, tasks, files, folders, and forms using our updated QUI library. The new design includes new icons, fonts, and colors while maintaining the same functionality. We also have a happy surprise, which is that we are also releasing an update to the List view in tasks that were originally planned for phase 2 of the redesign of the FLP.
Updates and performance improvements
Move a File or Folder
We have made further improvements to the Files hub, making it easier to move files and folders. You can follow the following steps to move a file or folder:
- Select the files/folders you wish to move.
- Select Move from the action bar.
- Navigate through the folder structure to your chosen destination.
- Select Move.
- Your files/folders will move to your chosen destination.
Bug fixes
- Resolved an issue where the task card summaries were not displayed when the dashboard picker was used.
New Frontline Portal HelpDocs content
- None at this time.
SOAP API / Web service updates
None at this time.
Please make sure to forward this information to the party within your company responsible for integrations.
