Version 0199

Updated by Leigh Hutchens

Release date November 14, 2024

Please note that Version 0199 has been postponed to allow for additional quality assurance. The expected release date is October 14, 2024.

Release summary

Short on time and want a high-level summary?

Quinyx web app Version 0199

New functionality

  • In this release we are introducing the possibility to configure clock-in restrictions for QClock (read more about QClock here).
  • With this release, we're enhancing our bulk actions functionality by introducing a new option in the Schedule view.

Updates and performance improvements

  • With this UI improvement to the Warnings Panel, you can now easily see the number of shifts that have warnings versus those that don’t. This enhancement gives you greater clarity on the impact of actions such as creating, editing, copying, and moving across multiple shifts simultaneously.
  • As of this release, warning messages for late schedule changes will now include an additional reminder for managers.

Bug fixes

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

Frontline Portal Version 0199

New functionality

  • None at this time.

Updates and performance improvements

  • None at this time.

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

Coming soon!

With the upcoming Version 0200 release, we are enhancing the wsdlFindEmployees SOAP API to include the email address in the response. This update allows you to better identify which email addresses are present in Quinyx and to associate them with the corresponding users, allowing you more flexibility in your setup. Read more here.

Release moved from November 27th to December 2nd, 2024

To ensure a smooth experience for our customers during the Black Friday sales period, we are rescheduling our upcoming release from November 27th to December 2nd, 2024. Although not all of our customers operate in retail, we recognize the importance of this peak season and aim to minimize any potential disruptions. Some scheduled payroll files will still be released as planned on November 27th.

Please note:

  • Final 2024 release: December 11th, 2024
  • First 2025 release: January 8th, 2025

Release highlight videos

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

Quinyx web app Version 0199

Release date November 13, 2024

New functionality

Clock-in restrictions for QClock

In this release, we're introducing the possibility to configure clock-in restrictions for QClock (read more about QClock here).

Organizations struggle with unexpected employee time. Employees may consistently clock-in 10 minutes early for a shift (because of a bus route, for example), and this excess time adds up to millions of dollars in large organizations. With this feature, employees can be blocked from clocking in by admin-designated time increments that can only be overridden by a manager.

Configure clock-in restrictions

To configure clock-in restrictions for your organization, follow these steps:

  1. Navigate to Account settings and click on Restrict clock-in under the QClock menu.
  2. Click on the add rule button in the top right corner.
  3. Give the rule a name.
  4. Define the number of minutes before or after shift start an employee is allowed to clock-in (anything outside of that will be restricted).
  5. Select one or multiple agreement templates that should use this rule.
  6. Click Save.

If you later wish to update or delete an existing rule, you just navigate to the same page and open the rule to update it, or use the trash can icon to delete it.

Clock-in when a restriction rule is configured

When a restriction rule is configured, employees will see a warning message if they try to clock-in outside of the allowed clock-in rule. The clock-in button will be disabled and the employee will not be able to proceed with the clock-in.

Manager override

Any manager within the organization can choose to override the clock-in restriction and allow the employee to clock-in even when they are outside of the configured clock-in restriction rule. To do that, the manager has to enter their badge number. The clock-in button will then be enabled, and if the badge number belongs to a manager the employee can proceed with the early clock-in.

This functionality will be available on web.quinyx.com and qclock.quinyx.com in the week commencing 18th of November.
Quick(er) bulk editing of the schedule view release #3 

In this release, we're enhancing the bulk actions functionality by introducing a new option in the Schedule view.

You can now add multiple unassigned shifts in a single action. Similar to the Base schedule view, can specify the number of unassigned shifts you'd like to add directly within the existing Add Shift panel.

Click the Save button, and the specified number of unassigned shifts, such as five shifts of the same type, will be created in the Schedule view.

This update streamlines the process, reducing the time and number of clicks required to add shifts.

New functionality requiring configuration updates

None at this time.

Updates and performance improvements

Warnings panel: Better visibility into shifts with warnings

With this UI improvement to the Warnings Panel, you can now easily see the number of shifts that have warnings versus those that don’t. This enhancement gives you greater clarity on the impact of actions such as creating, editing, copying, and moving across multiple shifts simultaneously.

Additionally, the same information will be available for the Base Schedule rollout, allowing you to track how many shifts have been successfully rolled out versus those that have warnings.

Updated warning message for late schedule changes 

As of this release, warning messages for late schedule changes will now include an additional reminder for managers. This will encourage managers to use the Offer Shift functionality, allowing them to get an employee's approval before assigning a shift that falls outside the defined schedule in the employee’s agreement.

Old message: Late schedule change.

New message: Late schedule change, we suggest that you offer these changes to the employees to get their approval.

Bug fixes

  • Resolved an issue where the last day of the published schedule was invisible in the notifications panel.
  • Resolved an issue where shifts couldn't be copied over longer periods.
  • Resolved an issue where employees and shifts took approximately 1 minute to load in the schedule view.

New Quinyx HelpDocs content

Frontline Portal Version 0199

Release date November 13, 2024

New functionality

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

New Frontline Portal HelpDocs content

SOAP API / Web service updates

Coming soon!

With the upcoming Version 0200 release, we are enhancing the wsdlFindEmployees SOAP API to include the email address in the response. This update allows you to better identify which email addresses are present in Quinyx and to associate them with the corresponding users, allowing you more flexibility in your setup.

Example request
<wsdlFindEmployeesRequest>
<apiKey>{{apiKeyDomain}}</apiKey>
  <emailList xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="tns:email[]">
   <email xsi:type="xsd:string">firstname.lastname@company.com</email>    
<email xsi:type="xsd:string">another.name@company.com</email>    
<email xsi:type="xsd:string">someone@company.com</email>    
<email xsi:type="xsd:string">one.more@company.com</email>
   </emailList>
</wsdlFindEmployeesRequest>

Example response
<wsdlFindEmployeesResponse> 
<return xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="tns:UnitEmployee[2]">    
<item xsi:type="tns:UnitEmployee">      
<api_key xsi:type="xsd:string">e121ererwrw121r2ewr12ew1r2e1wr2we1r21</api_key>      
<unitName xsi:type="xsd:string">Restaurant Foodie</unitName>      
<employeeId xsi:type="xsd:int">123456</employeeId>      
<email xsi:type="xsd:string">firstname.lastname@company.com</email>    
</item>    
<item xsi:type="tns:UnitEmployee">      
<api_key xsi:type="xsd:string">5r46ew4r564ewr5e4wr54ew65r4f5ds4f6</api_key>      
<unitName xsi:type="xsd:string">Restaurant The Best Food</unitName>      
<employeeId xsi:type="xsd:int">123457</employeeId>      
<email xsi:type="xsd:string">another.name@company.com</email>    
</item> 
</return>
</wsdlFindEmployeesResponse>

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?