Version 0151
Updated
by
Leigh Hutchens
Release date January 11, 2023
Release summaryShort on time and want a high-level summary? Web app
SOAP API / Webservice updates
Bug fixes
|
New functionality
Base schedule roll out considers Absence type affects schedule setting
If you manually create an absence on top of an existing shift in Schedule in Quinyx at the time of writing, the value in the Shifts in this period field will default to the selected absence type’s value in the absence type setting called Absence type affects schedule. The original purpose of this behavior was to reduce the amount of selections you as a user need to make when creating an absence. In the below example, as the absence type “Parental leave's Absence type affects schedule setting is set to Unassigning shifts, the Shifts in this period sets to Unassign automatically when Parental leave is selected in the Absence type field by the user.
However, up until this release, when you rolled out a base schedule on top of an absence, the shifts rolled out would not consider the Absence type affects schedule absence setting. In order to improve the user experience, as well as to make the system more consistent, this has now been addressed. See the screenshots below as an illustration of the changed behavior.
Pre 0151
If the base schedule rolled out looks like this:
it leads to the following outcome when rolled out over the absence type Parental leave whose Absence type affects schedule setting is set to Unassigning shifts:
Post 0151
If the base schedule rolled out looks like this:
it leads to the following outcome when rolled out over the absence type parental leave whose Absence type affects schedule setting is set to Unassigning shifts:
Norwegian self-certified sick leave and non-worked days (egenmelding)
The Norwegian self-certified sick leave (“egenmelding”) absence type setting enables support for Norwegian customers to ensure that their employees take no more absence days of this type than they’re entitled to by law. However, until this release, the logic in question was more lenient than Norwegian law prescribes; we've addressed this in this release.
Pre 0151
If the Max absence in employer period = 3 and the employer period = 16:
As you can see from the above screenshot, before, the maximum number of self-certified sick days - governed by the Max absence in employer period as described in the above link to our user manual - would not distinguish whether or not an employee came back to work after a self-certified absence, whereas now it will.
Post 0151
If the Max absence in employer period = 3 and the employer period = 16:
The above illustrates that after the changes introduced in this release, it is only if the employee comes back to work - interpreted by the system as there being a punch on a day subsequent to a day containing a self-certified sick leave - that the counting of absence day stops the day of the last self-certified absence. If they don’t return to work, the counting continues, which is why it’s impossible to add a self-certified sick leave in the last screenshot above.
Selecting Aggregation Type on variables
We've added an option to select aggregation type on Input Data, Forecast Configuration, or Optimal Headcount variables on the Variable Settings page. Until now, when viewing data on a higher aggregation than the existing data, Quinyx has summed all the data values on the selected aggregation level. For example, when visualizing the daily data points, it has been a sum of all individual data points within the day. However, whenever the data variable represents headcount or percentage variables, summing these up is not logical. We've added the option to select between Average and Sum on each variable.
When Sum is selected, no changes are made to the current aggregated data calculations.
When Average is selected, instead of summing up the values to show the daily total, Quinyx instead shows the daily average. The same holds when viewing data in the daily, weekly, or monthly view. The average is calculated by accounting for the values of each bucket with existing data and then calculating the average value based on those number of buckets.
For Forecast Configuration variables, the aggregation type, by default, is the same aggregation type as the one selected for the underlying Input Data.
By default, all existing Input Data, Forecast Configuration, or Optimal Headcount variables will have Sum as their aggregation type, and as such, no adjustments are made to the current aggregation calculations. When you add a new variable, Input Data variables will by default have Sum, while Optimal Headcount variables will by default have Average as the selected aggregation type.
Updates and performance improvements
Up until this release, the All day checkbox in the Add absence / Edit absence panel was ticked by default. Many of you gave us feedback about the sub-optimal user experience this entailed. As a result of this feedback and of our own research, the checkbox in question will be unticked moving forward. If you untick the checkbox after having ticked it, the date and time fields will contain the same data they had right before you ticked the checkbox.
Bug fixes
- Resolved an issue that caused shifts to overlap each other when viewing the schedule in day view.
- Resolved an issue that prevented attesting a shift in day view when there were concurrent shifts.
- Resolved an issue entailing that, once activated on a certain absence reason, the Define a max number of hours setting couldn't be properly deactivated.
- Resolved an issue that caused an employee that was first deactivated and later reactivated on a unit via API call UpdateEmployee to not have an active role on the unit and prevented that employee from being scheduled.
- Resolved an issue that prevented a UT period from being added to an agreement template.
- Resolved an issue where Punch (out) did not get rounded to shift end time unless split punch on tasks was disabled and punch was added through API.
- Resolved an issue with shifts remaining connected to an expired agreement when shifts were added via API call even if a new agreement was added later.
- Resolved an issue with Shifts to approve requests remained on an old home unit when a home unit was updated through wsdlUpdateEmployees.
- Resolved an issue where accrual Time Tracker, when defined as Don't accrue on the 7th day of the week still deducted the 7th day on the TimeTracker but not the 6th day.
New HelpDocs articles
SOAP API / Webservice updates
- wsdlUpdateUnit : output maxHourDay and maxHourWeek incorrectly listed as "int" in WSDL, documentation & response. But was in reality "dec", this has now been resolved and is returned correctly and schema updated.
- wsdlUpdatePunches : validation added to not allow updates to punches transferred to payroll.
- Resolved an issue where Punch (out) did not get rounded to shift end time unless split punch on tasks was disabled and punch was added through API.
No endpoints are currently deprecated and planned for removal.
Please make sure to forward this information to the party within your company responsible for integrations.
