Version 338
Quinyx WFM v338 has now been released. Version 338 contains a number of new features and bug fixes.
New features
- Support for punches longer than 24 hours
- New gender functionality
- Changes to delete employee functionality
- Cost centre now changes when a manned or unmanned shift is updated with a new shift type
- Added support for Traditional Chinese
API / Web Service updates
- wsdlUpdateEmployees in regards to gender
- Agresso service wsdlUpdateRelEmployees in regards to gender
Support for punches longer than 24 hours
In this release of Quinyx WFM we have added support for punches that are longer than 24 hours. This functionality will be part of Quinyx’ standard functionality and does not require any settings changes or other configuration.
This means that many views that contain punch details have changed and now show both start date and end date.
We have completely rebuilt the basics for punches in regards to start and end date together with start and end time. Multiple reports have also been rebuilt in order to reflect the new information. We are doing this as a step to be completely compatible with shifts longer than 24 hours which we will build support for during Autumn 2018.
Since punches now can be “infinite” in length we advise that you check your automatic punch out settings on your agreement templates. This setting can be found under Time → Agreement Templates→ Chosen template→ Time → Automatic punch out after.
The punch logic is unchanged, so punched hours will still belong to the start date of the shift the punch is connected to.
New gender functionality
We have updated the gender functionality Quinyx WFM. It is no longer mandatory to set the gender when creating a new employee and we have also added a third gender.
The default gender setting for a new employee will now be Other. It is possible through access rights to remove the gender setting from the employee card.
When Other is selected, the default profile picture will be set as in the above example. Defined reports with gender support all gender options.
Changes to delete employee functionality
We have made it more difficult to delete an employee by accident with this release.
The “Delete” button will be inactive (greyed out) unless the following criterias are met:
- The status of the employee is inactive (employed is unchecked on the employee card)
- The leave date is earlier than “Today’s” date
The “Delete” button is also moved to the left side of the window.
Cost centre now changes when a manned or unmanned shift is updated with a new shift type
We have changed the behaviour for cost centre changes on a shift when you change the shift type on the shift. This means that the cost center inheritance is always triggered when shift type is changed for the shift, regardless if cost center is set or not on the actual shift. Description of the cost center inheritance can be found here.
These changes affect both manual changes of shift types on app.quinyx.com and also shifts updated through wsdlUpdateShifts.
API / Web Service updates
- wsdlUpdateEmployees
- Added support for “sex = Other” via an integer set to 2
- wsdlUpdateRelEmployees (Agresso service)
- Added support for “sex = Other” via an integer set to 2
Bug fixes
- Corrections to transfer to payroll regarding dates and different time zones
- Transfer to payroll now locks salary period when there is no selection on unit as long as there are transferred transactions on the unit
- Fix for Punched hours report in regards to nominal hours being reduced on a bank holiday where there is no shift
- Fix for Punched hours report in regards to grouping per day which now correctly calculates punches without matching shifts
Neo Schedule (beta)
New features
Reset password
As of this release, you will be able to reset your password from the Neo login page.
Click on “Forgot your password?” under the login button, add the email address that you have registered in Quinyx, and you’ll receive instructions on how to change your password. The new password must comply with the selected security level (see below) and is used on all Quinyx platforms.
Standard
Standard level requires that all passwords are at least 6 characters long. If a manager resets an employee's password, or if the employee chooses to reset the password, the system will require that you choose a new password when logging in. The user account will be blocked after 12 unsuccessful login attempts. A manager must then reactivate the account.
High
The higher level involves the same changes as above, except that it also requires that the password is at least 8 characters, at least two of the characters must be numeric and two must be letters. The system will require a new password every three months, and you may not use the same password more than once during a 30-month period or 10 consecutive password changes. The user account will be blocked after 6 unsuccessful login attempts. A manager must then reactivate the account.
