Version 0202

Updated by Daniel Sjögren

Release date January 8th, 2025

Release summary

Short on time and want a high-level summary?

Quinyx web app Version 0202

New functionality

  • We're excited to announce that we are launching a brand-new design for our Android and iOS apps.
  • With this release, managers can now offer a single shift to multiple employees at once.
  • Managers can now leave a comment in the Notifications panel of the Manager portal before approving or denying a shift swap.
  • With this release, we have re-enabled support to export your Advanced Analytics dashboards as PDFs.

New functionality requiring configuration updates

  • We’ve introduced a new configuration under Agreement Templates > Absence Types to allow organizations to define whether a user can approve their own absence, per absence type, as controlled by the agreement template associated with the employee.

Updates and performance improvements

  • Through feedback, as of this release, we’re changing the Metric display mode default from Totals to By agreement.
  • As of this release, we’ve replaced the date picker when updating shift types in Account settings and Group settings.

Bug fixes

  • You might be interested in one of our bug fixes in this release. For more information, click here.

Frontline Portal Version 0202

New functionality

  • None at this time.

Updates and performance improvements

  • Coming this year! A new design for the Frontline Portal.
  • With this release, we have improved the visibility of folders and subfolders shared with your audiences.

Bug fixes

  • None at this time.

SOAP API / Webservice updates

  • Check out the updates and links to documentation here.

Important announcements

Scheduled Maintenance on January 28th, 2025

Dear valued Customer,

Please be informed that maintenance will take place as the team will upgrade our database system for Workforce Management.

European Customers

The scheduled maintenance will take place on January 28, 2025, at 21:00 Central European Time (CET).

North American Customers

The scheduled maintenance will take place on January 28, 2025, at 3 am Eastern Standard Time (EST).

During the scheduled maintenance, we anticipate limited disruption but:

  • it will result in a brief downtime of the Quinyx service for up to 30 minutes
  • we will temporarily suspend all incoming traffic to the database during the upgrade window

Should you have any questions or concerns regarding this upgrade, please do not hesitate to reach out to our support team.

Thank you for your understanding and cooperation as we work to enhance our systems and provide you with the best possible service.

Best regards,

Quinyx Team

Important information to Customers who didn't have access to release notes Version 0174 and Version 0193

Amazon Web Services

For good order, we want to inform you that Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855, Luxembourg, is the entity Quinyx engages as a sub-processor for hosting services. In case the applicable data processing agreement refers to a different Amazon Web Services entity (e.g., Amazon Web Services Sweden AB) it shall hereby be considered updated accordingly. 

For clarity, this change merely reflects our formal contractual relationship with Amazon Web Services and does not affect the actual processing of personal data (servers, hosting location, security measures, etc.; all remain the same).

New training environment

We are also happy to inform you that we have been developing a training environment together with a partner of ours. In this environment, videos and other generic training material regarding our service will be made accessible for a limited number of select users. In order to access and use this environment that is separate from your Quinyx environment, processing of certain basic account information (contact information, title, department, region and whether training has been completed or not etc) constituting personal data will be required. If you are invited to use this training environment, Attensi AS, Forskningsparken, Gaustadalléen 21, 0349 Oslo, Norway will be added as a sub-processor under the data processing agreement forming part of your agreement with Quinyx.  

Removed sub-processor

We also want to inform you that Intercom R&D Unlimited company is no longer used as a sub-processor under your data processing agreement (if applicable). For clarity, other than as set out above, no changes are made to the data processing agreement and no further action is required on your part. 

Quinyx Trust Center

For our customers’ convenience, we have launched Quinyx Trust Center in which you are welcome to read more about our sub-processors. 

If you have any questions or feedback, write to us via dataprivacy@quinyx.com.

Release highlights

To help you get the most out of this release, we've created a few highlight videos showcasing key updates and new features. 🎉

Quinyx web app Version 0202

Release date January 8th, 2025

New functionality

New design in the mobile apps and new side menu logo option

Our mobile team is excited to announce that we are launching a brand-new design for our Android and iOS apps, with mobile version 3.41 shortly after version 0202 has been released.

With this new design, the side menu in the mobile app will have two different colors depending on the mode the user's phone is set to. This is different from the current version, where the side menu always has a dark color, no matter if the user is in light or dark mode. This means that the users, from when the new design is implemented, will have:

  • A light color if they have light mode
  • A dark color if they have dark mode

To support this change, we’ve added a new setting under Account settings > Appearance > Navigation Bar, enabling you to upload two logos for the side menu.

This is the logic:

  • The current logo upload function for mobile was previously called “Company logo URL for mobile” and is now called “Company logo URL for mobile in dark mode.” This logo upload is the current function that will work for the current and older mobile versions. There is no need to change this logo since it will be automatically applied for users with dark mode once they’ve installed the coming mobile Version 3.41 of the app. The optimal logo size is at least 796px wide, and we recommend a logo with a white or light color if possible, the same recommendation as before for this option.
  • We’ve implemented a new logo upload function called “Company logo URL for mobile with light mode.” We recommend that you upload this logo as soon as possible since it will be shown to users with light mode selected on their phones and displayed once they install the coming mobile Version 3.41. The optimal logo size is at least 796px wide, and we recommend a logo with a black or dark color if possible.

If you don't upload any logos in one or the two options, the classic Quinyx logo will be shown.
Offer shifts to multiple employees

We’re excited to introduce a new enhancement to our Shift offer functionality. With this update, managers can now offer a single shift to multiple employees at once. This streamlines the filling open shifts and reduces the time it takes to find a suitable employee.

How It Works:

  • When creating a shift offer, managers can select multiple employees in the "Employee" field.
  • Once the shift offer is saved, all selected employees will be notified via Qmail and the mobile app.
  • The first employee to accept the offer will be assigned the shift, while all other employees will be notified that the offer is no longer available.

This improvement makes shift management more efficient and helps you quickly fill vacancies while keeping employees informed.

Manager comments on shift swap requests

Based on valuable feedback from our users, we're excited to introduce a new feature that allows managers to add comments when handling shift swap requests.

What’s New: Managers can now leave a comment in the Notifications panel of the Manager portal before approving or denying a shift swap. This feature enhances transparency by providing employees with clear explanations for manager decisions, particularly when a swap is denied.

  • The comment will be visible to employees in the Qmail they receive.
  • Managers can also view these comments in the Shift swap audit logs for future reference.

Looking Ahead: In upcoming releases, we’ll expand this functionality to include Shift booking and Shift unassignment requests.

Thank you for your continued feedback in helping us improve the product!

PDF Export for Advanced Analytics

With this release, we've re-enabled support to export your Advanced Analytics dashboards as PDFs so that you can easily share and distribute your insights as you see fit. PDFs can be generated in different sizes and printable formats (as well as, alternatively, exported as a CSV).

New functionality requiring configuration updates

Permission for users to approve their own absences

With this release we’ve adding a new permission, to allow you to configure whether users should be able to approve their own absences.

Under Agreement Templates > Absence Types you select whether users on that agreement template should be able to approve which, if any, of the absence types available to them.

For example - if, as an organization, you want local managers to be able to approve their own sick days but not their own vacations you can configure that accordingly in their agreement template.

Who can actually approve their own absences?

Employees with the employee role only have access to the Staff Portal, which is limited to submitting absence applications. They do not have access to the Manager Portal, where absences can be reviewed and approved. As a result, employees cannot approve any absences, including their own.

On the other hand, only users with the manager role and the necessary Absence Write permissions have the ability to approve absences. Even in the case of managers, the new "approve own absence" configuration only applies after all existing validations have been performed. This ensures that no employee or manager can bypass established permissions

That is - the new "user can approve own absence" configuration does not override any existing validations. It is an additional layer of validation. Before the system considers whether a manager or employee can approve their own absence, all existing validations are applied first to ensure the user has the role-based and other necessary permissions to approve absences in general.

Only after all other validations pass does the system check if the absence belongs to the user and if they have permission to approve their own absence. By default, the configuration is enabled for all absence types to maintain the current behavior and avoid breaking existing setups. This should require an explicit decision from the customer to disable it for each absence type.

Updates and performance improvements

Metric display mode default leveraging agreement information

Many of you have requested a piece of functionality that’s already supported in Quinyx, namely that of making the name of the agreements in use more easily accessible when working on or monitoring your employee’s schedule. This information is already available on hover when the “By agreement” option of the Display options > Metric display mode is selected. Thanks to your feedback, it has come to our attention that many of you are unaware of this feature but find it very valuable once you’re made aware of it. For that reason, as of this release, we’re changing the Metric display mode default from Totals to By agreement for all manager portal users as an exceptional, one-off measure. This applies to both for Schedule and Base schedule. Note that each user can change it back as per their personal preferences.

Date picker updates

We’re continuously replacing the date pickers in Quinyx. This is beneficial to our system’s technical health, and the difference is barely noticeable to the human eye. As of this release, we’ve replaced the date picker in Account settings > Shift types > Update shifts as well as in Group settings > Shift types > Update shifts.

Bug fixes

  • Resolved an issue where changing an absence request to All day would change the dates to yesterday's date.
  • Resolved an issue that caused tags not to be inherited from absence shifts.

New Quinyx HelpDocs content

  • None at this time.

Frontline Portal Version 0202

Release date January 8th, 2025

New functionality

None at this time.

Updates and performance improvements

Coming this year - a new design for the Frontline Portal

During the first part of 2025 we will be working with updating the look of our Frontline Portal with a brand new design. This new design will be released in phases. You can find the phases we are currently planning to deliver the new design in and some examples of how this will look here. More information about the exact dates of release will be shared in our release notes next year!

Improved audience visibility for shared folders

Previously, it was difficult to determine whether or not a folder was sharing its audience with all subfolders. To help make this clearer, you will now see an icon on folder cards when a folder is no longer sharing its audience with all subfolders. The icon is displayed on the parent folder card and, when hovered over, reads 'Audience not shared to all subfolders'.

Bug fixes

  • None at this time.

New Frontline Portal HelpDocs content

  • None at this time.

SOAP API / Web service updates

Click here to view the new Quinyx WFM Web Service documentation. You can find even more web services info here.
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?