Version 0113

Updated by Maria Lindberg

Release date July 28, 2021

New functionality

Schedule

Default sorting for drop-down menus

We’ve added default alphanumeric sorting to all Schedule drop-down menus.

Skill validation on task level

Quinyx now has skill validation on task level in Schedule so that a manager is notified if an employee doesn’t have a skill required for the task assigned to the selected shift time. The manager has the ability to approve or deny the warning:

Change Schedule view

You can now easily change the day, week, month, and custom views easily by clicking the icons on the upper left side of the schedule instead of selecting the view in the drop-down menu:

Icon for booking requests

We’ve added a new icon with a waving hand to more easily indicate booking requests on unassigned shifts:

Shift bookings

Quinyx now displays booking requests at the top of the smart list when you click on an unassigned shift:

Extended absence limit

We've increased the maximum absence limit from 12 months to 24 months:

Base schedule

Skill validation on task level

Quinyx now has skill validation on task level in Base schedule so that a manager is notified if an employee doesn’t have a skill required for the task assigned to the selected shift time. The manager can approve or deny the warning:

When rolling out a Base schedule, a manager is now notified if an employee doesn’t have the necessary skills required for a task assigned to a shift being rolled out. The manager can approve or deny the warning:

Updates and performance improvements

  • Added functionality to tick/untick all display options in the Forecast Overview adjust view sidebar.
  • Added functionality to be able to define eligibility rules for bank holidays on agreement templates. Eligibility rules still need to be created through SOAP API, but with this functionality they can be defined on selected agreement templates through the Quinyx GUI.

Bug fixes

  • Resolved a Base schedule break calculation issue that did not set a break if a shift began at 00:00. 
  • Resolved a Base schedule issue that produced a warning of overlapping shifts when the shift was re-rolled out. 
  • Resolved a display issue that caused the calendar box in the time card to be cut off by the Time Tracker transactions table.
  • Fixed an issue where break times on a shift displayed differently on a PC vs a MAC in some cases.
  • Resolved an issue regarding wsdlUpdateShifts when sending an invalid ScheduleId.
  • Correction to Punched hours report, in some cases, showing wrong hours when shift and punch overlaps two calendar days.
  • Correction to Punched hours report values is some cases being different from time card.
  • Correction to Time Tracker when configuration set to view balance as of specified day of year.
  • Resolved an issue that prevented some users from generating the Absence percentage report.

New HelpDocs articles

REST API / Web service updates

None at this time.

SOAP API / Web service updates

None at this time.

Endpoints being deprecated and removed

The following SOAP API endpoints will be discontinued and removed from Quinyx WFM August 2021. They are already now replaced with REST API endpoints for Quinyx Forecast or obsolete. Read more about Quinyx Forecast and the improved functionality here and about the new REST APIs here.

6.2 wsdlGetForecasts

6.3 wsdlUpdateForecasts

6.5 wsdlGetMonthlyView

6.6 wsdlUpdateForecastV2

6.8 wsdlUpdateForecastsV3

6.4 wsdlGetSalesData

6.9 wsdlGetSalesDataV2

6.7 wsdlGetOptimalStaffing

4.6 wsdlUpdateAdminGroupRelationships <- not applicable for Quinyx WFM

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?