Version 0121

Updated 1 week ago by Marcus M. Winkler

Release date November 17, 2021

Upcoming functionality

Upcoming change to Schedule Statistics

We're currently developing functionality to create display groups in Schedule Statistics, similar to that which we have already supported in the Forecast tab. This will allow you to select which variables you want to display in Schedule Statistics, Dashboard, and Forecast Overview, as well as group different data types and variables onto a single graph.

This additional flexibility means that when this functionality is released, users will be required to set up display groups to define which data is accessible in Schedule statistics before they are able to see any variables in Schedule Statistics, including optimal headcount calculations. This must be done by someone with access to Account settings > Variable settings. We will provide more information about how this can be configured closer to the release.

New functionality

Improved notification panel

As mentioned in version 0120 release notes, we have made improvements inside the notification panel.

Inside the panel

We've restructured the sections inside the panel, split them into new categories, and made it easier to take actions on the notifications:

These are the new categories:

Shift bookings

Displays shift bookings that requires manager approval.

Shift swaps

Displays shift swaps that require manager approval.

Absence requests

Displays absence requests sent in by your employees.

Unassigned shifts

Displays all unassigned shifts.

Notice of Interests

Displays all notice of interests submitted by your employees.

Shift unassignment requests

Displays all shifts where employees have asked to be unassigned from a shift.

Shifts to approve

Displays shifts on away unit that require approval from the home unit manager.

Take action on notifications

To take action on a notification, simply click on it and decide what type of action you would like to take:

Detailed information about each category will be added to this article in the coming days

Webpunch login URL configuration

We've added support to manage Webpunch login URL configurations.

Add, edit, and delete Webpunch login configurations

In Account settings > Webpunch > Webpunch login URLs, you can fully manage and configure unique Webpunch URLs for each of your available units:

Click here to read about setting up Webpunch and how to use the login URLs.

Updates and performance improvements

None at this time.

Bug fixes

  • Resolved an issue that prohibited Time Tracker transactions from being updated in the transaction view and the salary summary views in the Time card.
  • Resolved a staff card  issue that didn’t allow the Reports to field to allow searching by employee number.
  • Resolved an issue that produced incorrect hours in Metrics display. 
  • Resolved an issue that caused a shift booking made on an away unit to not display in notifications on an employee’s home unit even when the setting shift assignment on away unit requires approval was on.

New HelpDocs articles

REST API / Web service updates

None at this time.

SOAP API / Webservice updates

None at this time.

Endpoints being deprecated and removed

The following SOAP API endpoints will be discontinued and removed from Quinyx WFM November 2021. They are currently not in use and are not relevant for current version of Quinyx WFM.

  • wsdlGetUnassignedShifts
  • wsdlInsertTimeRecords
Click here to view the new Quinyx WFM Web Service documentation. You can find even more web services info here.
We encourage all our customers to make use of our APIs to maintain data and make sure that information is up to date. To ensure scalability of our APIs while growing our customer and user base, we have decided to add restrictions on usage of our SOAP APIs. These restrictions will be enforced programmatically and means that 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 following 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?