Version 0201

Updated by Victor Jespersen

Release Update: The original release date for this update was planned for December 11th, but we’ve decided to move the release to December 17th to allow for additional quality assurance. This extra time ensures we deliver the best possible experience to our users. Thank you for your understanding!

Release date December 17th, 2024

Release summary

Short on time and want a high-level summary?

Quinyx web app Version 0201

New functionality

  • With this release we’re introducing an Advanced Reminder History, which lets you get a better overview of your reminder activity.
  • With this release, we're enhancing the bulk actions functionality by introducing two new options in the Schedule view.
  • We have introduced the second, out of many to follow, scheduling KPIs: Scheduling Accuracy KPIs. Keep reading to learn more!

New functionality requiring configuration updates

  • Coming soon! New design in the mobile apps and new side menu logo option!

Updates and performance improvements

  • With this release, we have added a counter representing the number of hours of a shift that is being created.
  • We’ve updated the available recipient types for leave type reminders to allow more control when configuring consecutive and non-consecutive leave reminders to help ensure that reminder notifications are being sent to the right people, at the right time.
  • We added one more origin for Publish schedule audit logs.
  • You are now able to add custom names to your scheduling KPIs.

Bug fixes

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

Frontline Portal Version 0201

New functionality

  • Coming next year! A new design for the Frontline Portal.

Updates and performance improvements

  • In this version, we have implemented support for more languages in the Frontline Portal. Read on to learn more!

Bug fixes

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

SOAP API / Webservice updates

  • Check out the updates and links to documentation here.

Important announcements

Scheduled Maintenance on December 9th, 2024

Dear valued Customer,

We would like to inform you about the scheduled maintenance of our Base schedule functionality, which will take place on Monday, December 9, to perform essential updates. This process is expected to last for approximately 30 minutes.

European Customers

The scheduled maintenance will take place on December 9, 2024, at 20:00 Central European Time (CET). 

North American Customers

The scheduled maintenance will take place on December 9, 2024, at 09:00 CET - 3:00 AM Eastern Standard Time (EST). 

Please note:

This downtime will take place outside of regular working hours to minimize disruption.

During this time, the Base schedule will be temporarily unavailable for all users.

We apologize for any inconvenience this may cause and appreciate your understanding as we continue to improve our service. If you have any questions or concerns, please don’t hesitate to reach out to our Support team.

Thank you,

Quinyx Team

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.

Quinyx mobile redesign release 3.41 pushed to January

In our last release notes, we mentioned that a new version with a new design of the mobile apps was planned to be released in December; this has changed. To ensure a smooth experience for our customers during the Christmas sales period, we are rescheduling the upcoming mobile app release 3.41 from December 2024 to January 2025.

Release highlights

To help you get the most out of this release, we’ve created a few tutorials and highlight videos showcasing key updates and new features. Check them out for a quick and engaging overview by clicking here

Quinyx web app Version 0201

Release date December 17th, 2024

New functionality

Advanced reminder history

With this release we’re introducing an Advanced Reminder History, which lets you get a better overview of your reminder activity. By navigating to Account settings > Advanced settings > Reminders > Reminder history, you can see a detailed history of all reminders triggered within your organization, to whom, and when.

Here, you can filter by date, reminder type, groups, or individuals to verify that reminders are being triggered as expected. This also allows you to proactively follow up, ensuring the right people are notified based on the correct criteria and at the appropriate time.

Quick(er) bulk editing of the Schedule view release #4

With this release, we're enhancing our bulk actions functionality by introducing two new options in the Schedule view. 

  1. With the first improvement, you can now add multiple assigned shifts in a single action.

Selecting multiple employees within the existing "Add Shift" panel will determine the number of assigned shifts that will be added after clicking Save.

When creating shifts this way, the agreement value will be defaulted to “Selected automatically”. This means that each individual shift, assigned to a selected employee, will be assigned the agreement that belongs to that specific employee following the regular agreement assignment logic. The value “Selected automatically” presented while creating the shifts will not be editable, but you can always edit the assigned agreement in the shift after it's created.

Similar to agreements, if cost centers are connected to individual employees, due to inheritance logic, we will follow that inheritance logic and the field will default to “Selected automatically”. In this case, the manager can always remove the automatically added cost center or select one manually that will apply to all created shifts. 

Functionality “Shift assignment on away unit is not currently available for creation of multiple assigned shifts. We are working on supporting that, but for now, we suggest that you use single-shift creation. 
  1. With the second improvement, you will be able to use a new option to update time, breaks, and tasks inside our existing Bulk edit panel. 

A new option in the time drop-down is called “Adjust time by earlier/later” and will allow you to extend or shorten all selected shifts by a specified number of hours and/or minutes.

When this option is selected, you will be presented with new fields to change the shift's start and/or end time and to decide if you want it to start/end earlier or later by the selected amount of hours/minutes. 

If this option is selected inside the time drop-down, to follow a similar logic, you can adjust breaks and tasks in a similar manner using new options called “Adjust to the new start time” or “Adjust to the new end time”. This option will adjust the time of the breaks and tasks for the same amount as selected in the time dropdown. 

When using filters to perform bulk edits in the Schedule view, changes will apply only to shifts, not tasks. Currently, it is impossible to filter and edit one of the multiple tasks assigned to a shift in bulk editing.

Example: If you have selected “End - Later - 1 hour” inside the time dropdown, this will extend the end time of selected shifts for 1 hour. Selecting “Adjust to new end time” inside breaks and tasks, will result in moving breaks and tasks by 1 hour later as well. 

Scheduling accuracy KPIs

In this release, we have introduced the second, of many to follow, scheduling KPI: Scheduling Accuracy KPIs.

Please note that this functionality is available to customers who have purchased the Forecast Module. If you haven't yet acquired this module and are interested in enhancing your forecasting capabilities, please reach out to your Quinyx account representative for more information.

What is the purpose of scheduling KPIs?

Scheduling KPIs are the first step to an improved schedule. Scheduling KPIs aim to help store managers verify the quality of their schedules during the schedule creation phase and look back at an already worked schedule with the help of several metrics. These KPIs are single metrics that are easily accessible and configurable on an organizational level so that you can ensure that your store managers look at the right metrics when creating their schedules.

The second scheduling KPI that is possible to configure is related to Scheduling Accuracy.

What are Scheduling accuracy KPIs?

Scheduling accuracy is an important KPI for local managers to be able to verify while creating a schedule whether they have scheduled the right team members at the right place at the right time. Scheduling accuracy is important for the local manager and also for the whole organization to ensure that you are not overscheduling during moments where there is less demand or underscheduling during peak moments. Overscheduling and underscheduling can have a negative impact on your scheduling costs, your employees' well-being and productivity, and customer experience (which in turn can result in lost revenue).

Scheduling accuracy is calculated based on your forecasted headcount need compared to your existing schedule, and it lets you know whether there are adjustments you need to make to your schedule to ensure that you are more prepared for the future.

In this release, we have released three scheduling accuracy KPIs:

  • Underscheduled hours: The number of hours you are underscheduled within the scheduling period selected
  • Overscheduled hours: The number of hours you are overscheduled within the scheduling period selected
  • Hit percentage: The percentage of total hours within the scheduling period selected where you are scheduling exactly according to demand.

How can you configure Scheduling accuracy KPIs?

Scheduling Accuracy KPIs can be configured in Optimization Settings > Scheduling KPIs. Scheduling Accuracy KPIs don’t require any additional configuration. You only need to select which Scheduling Accuracy KPIs you want to consider. You can choose one or multiple of the Scheduling Accuracy KPIs available.

Select Create and then Scheduling Accuracy.

You can then select one of the three available scheduling accuracy KPIs and customize the name displayed on the scheduling page if you'd like a different label. Additionally, a short description of each KPI is provided for your reference.

Hit Save whenever you’re ready. If you also want to add another scheduling accuracy KPI, you just have to go through the same process again.

If the KPI has been selected to be shown on the Schedule page, you will now, when selecting the target icon in the schedule view, see the newly added KPI together with all other scheduling accuracy KPIs or productivity KPIs you have added.

Calculation details

Independently of what data granularity you have on your underlying forecast data, which impacts your optimal headcount data, we calculate all Scheduling Accuracy KPIs based on hourly data. For example, if you have optimal headcount data on a 15 minute level we will use the hourly average before calculating the Scheduling Accuracy KPIs.

Over scheduled hours are calculated by comparing the hourly averaged total optimal headcount to the hourly averaged total scheduled headcount and summing the total headcount hours where scheduled headcount is above the optimal headcount hours. E.g. If the optimal headcount is 2 and the scheduled headcount is 4 for two hours in a row then you have 4h of over scheduled hours

Under scheduled hours are calculated by comparing the hourly averaged total optimal headcount to the hourly averaged total scheduled headcount and summing the total headcount hours where scheduled headcount is below the optimal headcount hours. E.g. If the optimal headcount is 5 and the scheduled headcount is 2 for two hours in a row then you have 6h of over scheduled hours

Hit percentage is calculated by taking the total number of hourly buckets where the scheduled headcount is exactly equal to the optimal headcount and comparing that to the total hours of the day. E.g. if you schedule exactly according to demand 2 hours out of the 8 hours, then the hit percentage is 2/8 = 0,25 = 25%.

Additional information

  1. You can add multiple scheduling accuracy KPIs.
  2. The scheduling accuracy KPIs are calculated based on the timeframe you’re looking at in the schedule view. If you’re looking at a single day, the KPI is calculated only for that day, while the weekly view would show the KPI based on data from that whole week.
  3. Different to how productivity KPI is calculated, scheduling accuracy KPI is NOT impacted by filters in the schedule view.
  4. The scheduling accuracy KPIs are recalculated quickly after the changes are made (you don’t have to click somewhere to manually recalculate them).

New functionality requiring configuration updates

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

Our mobile team is excited to announce that we are currently implementing a brand-new design for our Android and iOS apps, launching with mobile version 3.41, planned for release in January.

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.

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 to them 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.

Below is a sneak peek of how the new design in the mobile apps will look for dark and light mode:

Updates and performance improvements

Hours count when creating a shift in the Base schedule

With this release, we have added a counter that represents the number of hours of a shift that is being created. This field already exists in the Schedule view, so we are adding it now in the Base schedule as well, for consistency reasons.

New recipient types for leave reminders

With this release, we’ve updated the available recipient types for leave type reminders to allow more control when configuring consecutive and non-consecutive leave reminders to help ensure that reminder notifications are being sent to the right people, at the right time.

Previously, when configuring a leave reminder, you had one option: the affected employee’s manager. This would send a notification to the corresponding manager, as defined in the “reporting to” field for that employee.

But with this release, we’ve added a second option with additional fallback logic, following the same design as the absence request notification logic, where if a “reporting to” manager is not defined the reminder will instead be sent to the next manager in line, according to your setup.

As such - we’ve also renamed the two available recipient options for leave type reminders, to better clarify this distinction:

  1. Affected employee’s reporting manager (previously called the “affected employee’s manager”).
  2. Affected employee’s reporting manager with fallback (the new option, with the fallback logic).
New origin for Publish schedule audit logs

We are adding one more origin for Publish schedule audit logs. We identified that we were missing the origin for all actions coming from publishing schedule through different integrations. For that reason, now “Via integration” will be the origin inside the “Action made by” column for the updates of the item “Publish schedule.”

Possibility to change the name of your Scheduling KPIs

You are now able to add custom names to your scheduling KPIs. Until now, the KPIs have all been called Productivity, but now you can give specific KPIs a name that is more relevant to you as a business.

The name can be changed in the edit panel of the specific KPI you want to change the name of, and your selected name will be visualized for that specific KPI on the scheduling page.

  1. Change the name of the KPI you want to call differently than the default name.
  2. View the changed name in the table.
  3. Notice how the new name is visualized on the scheduling page for all your units.

Bug fixes

  • Resolved an issue where the start time of absence requests changed unexpectedly when entering an end time in the Staff portal. 
  • Resolved an issue where accepting a shift offer returned a "Something went wrong" error, preventing successful approval of the shift. 
  • Resolved an issue where managers could not create shift offers at the section level, as the "Offer shift" option was missing in the edit shift panel despite the correct settings being enabled.

New Quinyx HelpDocs content

Frontline Portal Version 0201

Release date December 17th, 2024

New functionality

Coming next 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!

Updates and performance improvements

New language support in the Frontline Portal

In this version we have implemented support for the following languages in the Frontline portal:

  • Thai
  • Indonesian
  • Vietnamese
  • Korean
  • Arabic
  • Hebrew

Bug fixes

  • Resolved an issue where changing the text color in the task description gave error messages.
  • Resolved an issue where you could not start tasks when the task was sent out using an imported list and specifying roles in the visibility filter.

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?