Version 0147

Updated by Leigh Hutchens

Release date November 17th, 2022

Release summary

Short on time and want a high-level summary?

Web app

  • With this release, we introduce the Newsfeed Publisher. This tool enables you to easily create, edit and publish news articles for your entire organization.
  • When you select which statistics variables to display in the Base schedule, you can now also edit a date field called Start date for statistics. This field allows you to determine which de facto calendar dates you want to view Schedule statistic variables for so that you can consider those when working on your base schedule if needed.
  • Improvements to the display group creation or display group management in variable settings. Instead of seeing a long list of variables when selecting which variables should be visualized in which display group, the variables are now sorted by variable type.

SOAP API / Webservice updates

  • Update to wsdlUpdateShifts in regards to field grabbable.

Bug fixes

  • We tweaked some things too small to notice or too difficult to explain. If you really want more details, click here.

New functionality

Newsfeed Publisher

With this release, we are happy to introduce the Newsfeed Publisher. This is our new and improved communications channel to enable you to easily create, edit, and publish news articles for your entire organization. Perfect for large-scale communications, the Newsfeed Publisher is designed so that you can now easily reach and build communications for your company, with tools to ensure you can reach exactly who you want when you want as well as measure your employee's engagement with your different announcements and communications.

Articles can be created and managed via the Newsfeed Publisher in the Manager Portal and will be published instantaneously in the News tab of all employees that you've chosen to share the article with.

As a new functionality in the Manager Portal, the Newsfeed Publisher is disabled by default for all roles other than your local Superuser or System Administrator. To start working with the newsfeed, please ensure that the newsfeed permissions are activated for the appropriate roles in your organization. Once enabled (under Account Settings > Role Management > Newsfeed) you should be ready to go!
For a detailed breakdown of exactly how the Newsfeed Publisher works, read more here.
A new article in the newsfeed publisher
Published articles in the mobile app's news tab

Updates and performance improvements

  • When you select which statistics variables to display in the Base schedule, you can also edit a date field called Start date for statistics. This field allows you to determine which de facto calendar dates you want to view Schedule statistic variables for so that you can consider those when working on your base schedule if needed. This field previously had an inconsistent effect on the dates displayed in the base schedule statistics past, so from this release, it will act as follows:
    • If you're in the weekly view and select, say November 7, in week 1 of your base schedule, it will display November 7-11 in the statistics. If, after having done that, you move to week 2 in your base schedule, then it will display November 14-20 in the statistics. That way, the statistics will accurately simulate your rollout of the base schedule as you step through your base schedule's weeks.
  • We've made a small improvement to the display group creation or display group management in variable settings. Instead of simply seeing a long list of variables when selecting which variables should be visualized in which display group, the variables are now sorted by variable type: standard variables, input data, forecast configurations, calculated variables, or optimal headcount to make variable selection into display groups smoother.

Bug fixes

  • Resolved an issue in the base schedule view where copied and moved shifts wouldn't change the cost center according to the staff card.
  • Resolved an issue in the base schedule view where a statistics variable showed a value of 0h.
  • Resolved an issue where base schedule salary cost didn't consider filter options made.
  • Resolved an issue for base schedules where copying shifts from employee A to employee B would automatically connect employee A's main agreement to it.
  • Resolved an issue in the base schedule view where it wasn't possible to assign unassigned shifts to employees with future agreement start dates.
  • Resolved an issue that made it possible to attest punches for a future date when it wasn't allowed.
  • Resolved an issue with the schedule statistics variable Actual Salary Cost showing an incorrect value when no employee filtering had been done.
  • Resolved an issue with compensation rules and absences counting as worked days even though setting includeAllAbsencesCountedAsWorkedHours = false.
  • Resolved an issue in wsdlGetSchedulesV2 that gave an Internal server error.
  • Resolved an issue with managers requiring read/write access to Forecast or Settings to view any data in schedule statistics. From now on either Schedule read/write permissions or Forecast Overview read/write permissions are needed to view data in schedule statistics.
  • Resolved an issue where store managers were unable to pull demand forecasts from Quinyx without full system access.

New HelpDocs articles

SOAP API / Webservice updates

wsdlUpdateShifts

Field "grabbable" will now reset to 0 when shift is reassigned or unassigned.

Endpoints being deprecated and removed

No endpoints are currently deprecated and planned for removal.

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?