From this release of Quinyx WFM (370), we have new improved logic in regards to bank holiday rule time off.
Previously, the logic for this rule was to place the generated salarytype(s) from the rule on a day closest to that day within the schedule period.
With the new functionality, the outcome is generated on the actual day the rule exists on. This will be done by introducing a “virtual shift”. This shift is not visible as a scheduled shift by the employee and also does not:
- count as scheduled hours
- count as worked hours
- count as a shift
With this functionality, the estimated salarycost will be even more accurate for individual days surrounding the bank holidays containing a rule for time off. It will also make it very visible where the outcome from a rule is generated.
A few things to take into consideration:
- A single virtual transaction cannot be reversed, but it will be reversed when reversing other transactions for employee or unit
- A virtual shift cannot be attested or unattested, they are always in the attest state
- Attest colour in Time view does consider virtual shifts
- If a shift or punch is added to a day, the virtual shift will be removed
- Since there is no shift in this day, the costcentre will be inherited from employee card or employee section or employee unit
You can read more about Bank holiday and rules on bank holidays here.
Updates and performance
- Payroll files updated to handle virtual shifts
- Reports updated .to handle virtual shifts
API / Web Service updates
wsdlGetPayrollV2: A virtual shift (see above) will be returned with schedule id "0"
wsdlGetPayroll: A virtual shift (see above) will be returned with schedule id "0"
wsdlGetSchedulesV2 : A virtual shift will be returned with status = 4 IF includeCosts = true. They will then be returned with scheduleid = 0 and ts = now
- wsdlUpdateEmployees . Solved an issue with sharing and the employee was new