Don't forget that mobile access rights is available in Neo now. Read more about how to get it up and running for your organization here!
New functionality
Staff portal
Book shifts / make shifts available
It's now possible to make your own shifts available for others to book. It is also possible to book shifts that are unassigned and have been made available for booking by colleagues. You can book an unassigned shift/colleague's shift by clicking "Book shift" in the shifts detail panel. You make your own shifts available for others to book in the detail panel as well.
Leave applications
As of version 0093, it's possible to see all approved, pending, and denied leave applications. It's also possible to create a new leave application and edit a pending one.
The Staff portal follows the mobile access rights.
Schedule
Part time absence on individual absence shifts
We're continuing to add additional absence functionality in this sprint. Now it’s possible to apply part time absence per individual absence shift.
How to:
Apply absence, select employee, from and to date, absence type.
Apply part time absence percentage under Part time absence:
Select what you want to do with the absence shifts.
All shifts in one go:
or
Per individual shift:
Select which action you want to apply on the absence shift(s):
Keep the start of the shift:
Unassign the last part of the shift.
Delete the last part of the shift.
Keep the end of the shift:
Unassign the first part of the shift.
Delete the first part of the shift.
Edit the whole shift:
Keep the whole shift.
Unassign the whole shift.
Delete the whole shift.
Note that you can bypass the part time percentage by selecting c) i, ii, iii above. (this is relevant for some of our Norwegian customers who want to include the percentage in the salary file at the same time as they want to keep the entire absence shift intact).
It’s not possible to apply different percentage rates on the same absence
As of this release it's also possible to change dates of a part time absence
Min/max value in Time Tracker balance
In a previous release, we added a visual indication in the Time Tracker balance to show if the the value was above or below the defined value. Now, we're able to give more precise information 1) Value is greater than max value or, 2) Value is less than min value and also what the defined value is within brackets:
Employee metrics calculation period in Schedule
As of this release, you’re able to determine for which period the employee metrics for all of the employees in the left-hand margin of the Schedule should display. This is set in the Employee list display options panel that we released in version 0092:
The selectable periods are:
Selected period: This is whatever period you’re currently viewing in Schedule.
Schedule period: This is configured in Agreement > Agreement template.
Balance period: This is configured in Agreement > Agreement template.
Just as prior to this release, schedule period is default.
As a result of feedback we've received from some of you (thanks!), we’re in the process of renaming employee KPIs to employee metrics; please note that for a release or so, you might see both appear in Quinyx.
Quinyx will not remember your selection if you leave the view and come back, nor if you switch period. This is, however, planned for our filter improvements - see ETA for “Filtering - improved” under the “Schedule” section in our external roadmap so sit tight!
Employee metrics calculation period in Base Schedule
We’ve also added the equivalent functionality to base schedule:
As base schedules don’t have dates, you have two options here:
Selected period
When this option is selected, the metrics will reflect the hours of the day or week you’re currently viewing for the employee in question.
Template period
When this option is selected, the metrics will reflect the hours of the full base schedule for the employee in question.
When it comes to the way agreement workdays are translated into nominal hours and you’re looking at the metrics of a specific day, the same principles apply in Base schedule as in Schedule:
If workdays are configured to 7, Quinyx considers every day as a workday.
If workdays are 6, Quinyx considers Monday to Saturday as workdays.
If workdays are 5, Quinyx considers Monday to Friday as workdays.
If workdays are less than 5, Quinyx currently lacks support for determining which weekdays are workdays. Therefore, for instance, if workdays are 4 and nominal hours 21 in the agreement, then the nominal hours of any day you’re looking at will display as 21.
As you move between different days or weeks in your base schedule, Quinyx remembers the selected calculation period. However, as you leave the base schedule and come back, your calculation period selection will reset - we of course plan to improve this in the releases to come.
The nominal hours displaying in the employee metrics are currently always for the main agreement only. This means the system goes by the number of workdays defined on the agreement that’s configured as main agreement as of today’s date.
Worked/Rollout hours employee metric
In the employee metric panel, we’re adding a new metric: worked hours vs rollout hours. This metric will be particularly useful for those of you aiming to use base schedule as an overtime method (when we release that soon), but it's also useful for anyone wanting to follow up on an employee's worked hours in regards to rolled out base schedule hours.
The data used in worked hours is the exact same ones as the ones in the worked hours vs nominal hours metric. The data used in the rollout hours is a snapshot of all the base schedule shift hours of the latest rollout of any one base schedule rolled out for the given employee.
A few details regarding the rollout hours:
This metric considers bank holidays reduction bank holiday setting, which can be configured to anywhere between 0% and 100%. This means that if you roll out 10 scheduled hours on a bank holiday configured to 70% reduction, then this will count as 3 hours towards the rollout hours endpoint. In order to not defeat the purpose of considering that setting, the metric doesn’t consider the “Schedule bank holidays” agreement setting.
This metric considers the “Count as scheduled hours” setting on shifts/shift types, as well as the “Calculate breaks as working time” agreement setting.
If you’ve rolled out a base schedule multiple times for a given employee, then the hours from each one of those base schedules are included.
The data reflects the period you’re viewing the metric for (selected period / schedule period / balance period), just like with the other metrics.
If the employee has a base schedule but it hasn’t been rolled out, rollout hours will be 0.
Updates and performance improvements
None at this time.
Bug fixes
For an unassigned shift, the UT salary is not taken into consideration for scheduled and expected cost calculation.
Resolved an issue that was deducting vacation balance from the current year instead of the least recent year when applying leave to a specific period.
Resolved an issue preventing a new employee from setting a new password when logging in the first time after a manager has set a one time password.
Resolved an issue that was considering old absence shifts when expanding absences to new shifts.
Resolved an issue that was preventing saving an agreement template when a space in an integration key was present.
Resolved an issue affecting changing an absence that displayed a message suggested deleting the shift instead of unassigning the shift.
Resolved an issue that was not correctly disabling an absence percentage rate when creating a part-time absence.
API / Web service updates
Please see Classic version 386 release notes for more information about API and Web services updates.
Updated
by
Leigh Hutchens
