Version 0204
Updated
by
Leigh Hutchens
Release date February 6th, 2025
Release summary
Short on time and want a high-level summary? Quinyx web app Version 0204 New functionality
New functionality requiring configuration updates
Updates and performance improvements
Bug fixes
Frontline Portal Version 0204 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 0204
Release date February 5th, 2025
New functionality
Schedule Validation 2.0
We're excited to announce the release of the beta version of Schedule Validation 2.0! This update brings enhanced features to help you manage your scheduling more effectively, including:
- Customizable rules: Selected customers can now customize which rules trigger warnings or hard stops, and even turn specific rules off.
If you’re interested in participating in this beta and providing feedback, please contact your Quinyx representative.
Shift offers audit logs
With this release, we include one more addition to our new audit logs framework, which is the logs for the new Shift offer functionality. With this addition, we provide more information and a bigger picture for managers to understand if some of the shift changes are actually coming from connected shift offers.
Searching for shift offer audit logs inside the Adjust view panel follows the same logic as described in the Audit logs (current) article with the following additions:
- We've added a new “Item type” called “Shift offer”.
Navigating the logs search results in our audit logs table follows the same logic as described in the Audit logs (current) article with the following adjustments:
- “Shift offer” is a separate item, meaning it will have its own separate row inside the audit logs table.
- Inside the “Timestamp” column, we display the date and time when a given action in Quinyx was carried out.
- Inside the “Groups affected” column, we display the units and sections that were affected by the action in question.
- Inside the “Item type” column, we display a new item type named “Shift offer”.
- Inside the “Item” column, we are showing the details of the shift for which the shift offer was created. Shift details include [Start date] [Start time] [End time] [Shift type name].
- Inside the “Action” column, we display actions taken on a shift offer, which fall into the following types: create, approve, deny, and delete.
- Inside the “Action made by” column, we display who has carried out the action in question.
- Inside the “Action made for” column, we display who was affected by the action in question.
- The shift offer item has additional properties assigned, and for that reason, you can expand the sub-table on the action to see more details about:
- Any comment that was added by the manager when the shift offer was created.
- This property is available only for the create action row.
- Shift offers as an item don’t have their own history trail, but the actions over shift offers will be visualized inside the connected shift history trail.
Shift offer action made by origin
Similar to other items, you can also see the origin associated with the shift offer item.
Origin provides additional insight into where the action reviewed took place. As highlighted in the image below, the origin information is located in smaller text below the main value in the Action made by column of the view.
The table below contains an exhaustive list of the various origin values you may encounter as you browse your log search results and the cases in which the values will display. The logic in the origin naming aims to support you in resolving disputes or issues concerning workforce planning and attendance and is as follows:
- In most cases, it reflects the Quinyx “platform” where the action got triggered, such as the Manager portal, Mobile, Webpunch, or Integration.
- However, suppose the action has been triggered by a specific feature that has cascading effects on other parts of Quinyx, such as deleting or reassigning the shift; this will display as the origin instead.
Action | Origin | Cases |
Creation | Via Manager portal | When a manager creates a shift offer in the Manager portal. |
Deletion | Via Manager portal | When a manager deletes a shift offer in the Manager portal. |
Deletion | Due to automatic deletion | When Quinyx as a system deletes automatically an offer that hasn’t been handled by an employee and the shift has already started. |
Deletion | Due to shift offer approval | When the shift is offered to multiple employees and it's approved by one, all other offers made to other employees will be deleted. |
Approve | Via Mobile | When an employee approves a shift offer in Mobile. |
Deny | Via Mobile | When an employee denies a shift offer in Mobile. |
New functionality requiring configuration updates
Coming: Support for logging in to the mobile app with Company alias and EmployeeID
In the coming mobile app Version 3.42, planned for February, we've implemented support for a new login flow we call "Company alias" and “Employee ID.” This makes it possible for our customers who can't use our regular supported usernames to have their users use a Company alias that points them toward the right customer in our system and then log in with an internal employee ID that could be a badge number.
The login flow for customers that use company alias and employeeID is the following:
- Step 1: In the “username or company alias” field, the user provides a “global alias” with a unique tenant ID.
- Step 2: In the next step, the user provides the employee ID or username. This and the following pages can also show a logotype of the customer's choice as a part of the login flow.
- Step 3: The user chooses which provider to use (password or SSO).
- Step 4: The user provides a password and gets logged in.
Log in with Employee ID and Company alias
We're expanding the login flow with two new options. First, we're introducing a Company alias that is a shorthand alias representing the tenant/account. This is set by Quinyx; reach out to us via a Support request to activate it.
You can use the company alias in the URL, for example:
https://web.quinyx.com/CompanyAlias
Next, enter your user ID, which can be your Login ID, email, or Employee ID.
Then, enter your password as usual to complete the login process.
If the login details are incorrect, a generic error message will be displayed in accordance with security policies.
What is Employee ID?
Employee ID is the external name for badge number. If you want your users to be able to use their internal employee number to log in you can update the user information by storing the employee ID in the Badge number field (20 characters maximum).
Badge number/employee ID is not unique across accounts/customers you need to state a Company alias via the url first to be able to log in.
Company Alias
A company alias is a shorthand identifier unique for the specific account in Quinyx. Quinyx sets it in the account/domain level in our Back office tool. It can be 50 characters long, and as it is used in the URL, it should not contain any special characters.
Selecting which units should be able to run the Auto Schedule or Auto Assign algorithm
We've added an option to specify which units users can trigger the Auto Schedule and Auto Assign algorithms for and which units they cannot. This provides greater control and helps prevent algorithms from being triggered for improperly configured units.
How can I configure it?
This setting can only be configured if you have purchased or use either of our algorithm modules: Demand Forecasting, Auto Schedule, and Auto Assign.
The units to run the algorithm can be configured in Optimization Settings > Algorithm settings. The Algorithm settings is a new configuration page within the Optimization Settings where, over time, we'll add more configuration options related to our algorithms.
Once you have selected Algorithm settings, you will see an option called Units enabled to run the algorithms. Selecting the edit icon opens up a group tree. You can either select individual units, a whole district (which will autofill all units within that district), or the entire organization (which will autofill all units within the entire organization). By default, the entire organization will be enabled.
The selection of units will control which units are available to select and which units are grayed out when trying to run the Auto Schedule, Auto Assign, or Demand Forecasting algorithm.
Updates and performance improvements
Coming: Mobile - restricting users from creating invalid absence requests in periods they don't have an active agreement
In the upcoming mobile version 3.42 planned for February, we are updating the absence request function in the mobile apps. With this update, if you don’t have a valid agreement during the dates you try to create an absence request, no absence types will show up in the absence types list, and the user will, therefore, be unable to submit an absence request. The absence request process and what absence reasons you can select are controlled by whether you have an active agreement during the dates you apply for absence. If you have an agreement template connected to your agreement, only the absence types for which the employee checkbox is ticked in Account settings > Agreement templates > Absence types will be visible in the absence types list. With this new restriction, we've changed the order of the fields in the "request a new absence" page so that the users choose the from and to date (and time) first so that Quinyx as a system can determine whether there is an active agreement during that time period.
Improved support for monitoring and editing shared employees' schedule
This release marks the beginning of a series of improvements made to Quinyx' current support for away-group shifts and absences in Schedule. The purpose of the changes we’re making is primarily to improve the ability to monitor and edit the schedules of shared employees, that is, employees that work across different Quinyx groups (which typically represent different geographical locations, subject to configuration) since absences and shifts in other locations are a factor to consider when creating or editing your employees' schedule. Our solution has presented particular challenges for those operating in the facility management industry.
Increased visibility of away-group shifts and absences
The following will now apply to Quinyx's user interface in Schedule:
- Away-group shifts, as well as away-group absences, will display as their own entities, i.e., as individual “boxes”. Refer to Gregory Payne’s shift and absence on Tuesday, where the 9 pm-11 pm vacation and the 7 pm-8 pm afternoon shift take place on the group selected in the group selector (= Drottninggatan) at the time the picture in question was taken. The two remaining absences of shifts of that day take place on a group other than that selected in the group selector.
- As you can see, the away-group items of one employee on any given day are currently not sorted chronologically in line with same-group items; this is something we plan to address in a release very soon.
- These new entities have an updated design compared to before, which aims to help distinguish away-group shifts from away-group absences. It also aims to improve the readability of both types of items. From now on:
- Away-group absences are recognized by a dark grey background, black slanted lines, and white text.
- Away-group shifts are recognized by a white background, light grey slanted lines, and black text.
As before, away-group shifts and absences are controlled by the filter category called “Unavailability” in the schedule filters.
The weekly view (the monthly and custom views use the same design pattern).
The daily view (the monthly and custom views use the same design pattern).
Our plan is for future releases on this topic to contain improvements such as:
- Displaying punches of away-group shifts.
- Displaying hour-count of away-group shifts and punches.
- Displaying away-group shifts and absences in the Schedule printout.
Quicker bulk editing of the Schedule - edit employees on multiple shifts
With this release, we are adding the “Employee” field inside the bulk edit shifts panel so that the employee value can be updated on multiple shifts. Selecting all shifts in the view or picking up a few of them, you can now quickly change employee value and reassign those shifts to another employee. Also, this improvement will allow you to remove any employee value on selected shifts and quickly make them unassigned.
How does this logic work?
- If you have selected shifts that are assigned to one employee (identical value) → this employee will be the default selection inside the drop-down. To change this selection:
- You can click on 'x' button to remove the employee value and to get to the “unassigned” value.
- You can, in the drop-down, select any other employee.
- What happens with agreement value in this case?
- The agreement field will be shown with the default value “Select automatically”, meaning that Quinyx will select a valid agreement based on the date when shifts are taking place.
- You can still manually select any other valid agreement from the list if you want one specific agreement to apply to all shifts.
- If, in the same panel, the date of selected shifts is updated, the list of agreements will be updated to represent valid agreements on that date.
- If an agreement is selected manually but it’s not valid on another date where the shift is updated, Quinyx will manually select another valid agreement.
- If you have selected shifts that are unassigned (identical value) → “Unassigned” will be the default selection inside the drop-down. To change this selection:
- You can select any employee from the list and assign all shifts to that employee.
- What happens with agreement value in this case?
- For this case, the agreement field will not be shown since we don’t show agreements for unassigned shifts.
- If you have selected shifts assigned to multiple employees → “Keep as is” will be the default selection inside the drop-down. To change this selection:
- You can click on 'x' button to remove the employee value and get to the “unassigned” value.
- You can, in the drop-down, select any other employee.
- What happens with the agreement value in this case?
- For this case, the agreement field will not be shown as there are multiple agreements connected to multiple employees, so Quinyx will keep agreements already connected to selected shifts.
- For this case, the agreement field will not be shown as there are multiple agreements connected to multiple employees, so Quinyx will keep agreements already connected to selected shifts.
Bug fixes
- Resolved an issue that caused transactions to transfer to a payroll file without an agreement.
- Resolved an issue causing users not to be able to create a punch that starts/ends the next day, even if the connected shift would span for two days.
New Quinyx HelpDocs content
Frontline Portal Version 0204
Release date February 5th, 2025
New functionality
None at this time.
Updates and performance improvements
- None at this time.
Bug fixes
- None at this time.
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.
