Version 351

New features

From the release of Quinyx 352 planned for release 2019-03-12 you will only be able to use wsdlGetUnits, wsdlGetUnitsAPIKey, wsdlGetRestaurants, wsdlGetRestaurantsAPIKey with the API key of the root store (main unit). Trying to use the calls above with an API key from a non root unit will result in an empty response from the Web Service. Main unit is identified from Settings→ Units

Reverse payroll transfer

As a first step to be able to reverse a completed transfer to payroll we have added the possibility to reverse transactions based on the choices made when transferring to payroll. This is done from Time→ File archive and the new option Reverse this payroll transfer. You will only be able to reverse payroll transfers that you have initiated and can download. Reversing of transactions are done as a background process and status is shown in the view.

Note: Use this functionality with caution if your current process is transferring payroll for the same period and users multiple times. The reverse payroll transfer uses the selected choices done in the original transfer to payroll dialogue and reverses all the users chosen for that period.
Example : User 1 has during January worked 9/1 and 10/1. Transfer to payroll is done from 1/1-14/1 and both dates and connected transactions are send to payroll and locked/updated. Then user works 24/1 and 25/1 and payroll is done from 1/1-31/1. In this case the last payroll wound be reversed all four dates and transactions would be reversed

Schedule period report

A new standard report is available under Reports & Statistics → Schedule → Schedule period report. This report will be generated by a background process and will be made available under Reports & Statistics → File archive when finished.

You have the option to base it on the schedule period or on the balance period on the agreement

  • Unit : Unit of where the agreement is connected to
  • Employee : Badge number and Full name
  • Agreement template : Template name of the agreement
  • From date : Start of schedule/balance period for agreement
  • To date : End date of schedule/balance period for agreement
  • Employment rate : % of employment rate for agreement
  • Nominal hours : Nominal hours in the From date - To date period
  • Total scheduled hours : Total of scheduled hours during the From date - To date period
  • Absence hours : Absence hours up until yesterday from start of period
  • Punched hours : Punched hours up until yesterday from start of period
  • Hours from today until the end of period : Scheduled hours from today until end of period
  • Absence hours from today util the end of the period : absence hours from today until end of period
  • Sum : Sum of Absence hours, Punched hours, hours from today, Absence from today

New option for salary type generation

It´s now possible to define on salary type level if a certain type should not be generated at the same time as another salary type.

Example : I do not want UT-8 to be generated at the same time as Overtime 4 paid.

To achieve this you define this on the salary type from Settings→ Tables → Salary type → Chosen salary type or Time → Agreement templates → Chosen agreement → Salary types

The above example will restrict UT-8 to be generated at the same time as OT4 paid.

Same time is defined as in the same time period. Eg if both UT-8 and OT4 paid where to be generated during 13:15 - 13:45 with this setting only OT 4 paid would be generated during this time. If overlapping times where present only the period overlapping would be affected.

API / Web Service updates

Security and stability is one of the things that we at Quinyx always works with during development. During the last months we have done improvements and additions to our Web Services. During this time we have found that we need to change some functionality in regards to the following API calls

·  wsdlGetUnits

·  wsdlGetUnitsAPIKey

·  wsdlGetRestaurants

·  wsdlGetRestaurantsAPIKey

From the release of Quinyx 351 planned for release 2019-02-19 you will only be able to use that above requests with the API key of the root store (main unit). Trying to use the calls above with an API key from a non root unit will result in an empty response from the Web Service. Main unit is identified from Settings→ Units

Click here to view the new Quinyx WFM Web Service documentation. More info can be found here

Updates and performance

  • Update to the agreement templates and agreements in regards to preparation for more mobile punching options.

Bug fixes

  • Fix for managers in manager groups on sections not seeing pending leave applications
  • Correction to an employee moved to another unit wrongfully keeping the section information
  • Correction to when a template is rolled out containing scheduled shifts connected to agreements on multiple units the correct agreement is now chosen

How Did We Do?