EmpowerHR 2025.0.02 hotfix release notes

We are pleased to present EmpowerHR 2025 Hotfix Build 0.02

What's new in 2025.0.02

Crossboarding issues

EMP-9505

Reported by:   Department of Fire and Emergency Services (DFES), Fusion5

Located at:  

Background Jobs > Bulk Data Take-On > Crossboarding > Crossboarding Process

Background Jobs > Bulk Data Take-On > Crossboarding > Crossboard Approval/Error Fix

Issues

1. Crossboarding via an API/Take-on file against an employee with one current employment fails if the current employment and position are not provided.
2. The Crossboarding Approval/Error Fix screen does not remove a record that is successfully crossboarded.
3. When crossboarding via an API/take-on file, EmpowerHR ignores the musts transaction rule.

Resolution

1. Crossboarding looks for the current employment and performs the movement against it.
2. The issue of Crossboarding Approval/Error Fix screen not removing a record that is successfully crossboarded has been fixed.
3. EmpowerHR now checks the musts transaction rule.

Crossboarding issues

iHelp: 541396, 540653 

EMP-9530

Reported by:   Department of Fire and Emergency Services (DFES), Department of Education, Tasmania, and David Jones

Located at:  

Background Jobs > Bulk Data Take-On > Crossboarding > Crossboarding Process

Issues

1. When doing crossboarding via API or bulk take-on, the Contract Reason and Contract Expiry Date does not work according to the transaction rule defol (default from previous movement), and the dati format of the Contract Expiry Date might not reflect the date format stored in the database.
2. When doing a transfer via crossboarding, if the current class level is higher than 01 and the class level column is left blank, the class level of the new movement record is set back to 01 rather than staying the same class level as the previous movement.

Resolution

1. The dati format field of the Contract Expiry Date is fixed to reflect the same date stored in the equivalent date format field.
2. Column V (Contract Reason) and column W (Contract Expiry Date) have the following rules:

   1. If the transaction rule defol is set to n and the take-on file has blank data for the columns, then EmpowerHR creates blank Contract Reason and blank Contract Expiry Date for the new movement record, otherwise EmpowerHR populates the fields with non-blank data from the take-on file.

   2. If the transaction rule defol is set to y and the take-on file has blank data for the columns, then EmpowerHR populates the new movement record with the previous movement's Contract Reason and Contract Expiry Date, otherwise EmpowerHR populates the fields with non-blank data from the take-on file. 

   3. If the transaction rule defol is set to y and you still want to make the two fields blank (that is, not populate them from the previous movement's data), then set column V (Contract Reason) in the take-on file to 9999 and column W (Contract Expiry Date) to 99999999.
3. The issue of the class level setting back to 01 is resolved.

Onboarding - fields not defaulting from class/level

iHelp:  550793

EMP-9646

Reported by:   Department of Fire and Emergency Services (DFES)

Located at:  

Background Jobs > Bulk Data Take-On > Position/Employee Data > Bulk Take-On Initiation

Background Jobs > Bulk Data Take-On > Position/Employee Data > Bulk Take-On Process

Issue

Resolution

Error running employee personal data update via API & crossboarding take-on (Oracle)

iHelp:  545959 

EMP-9690

Reported by:   Department of Premier and Cabinet (DPaC)

Issue

This only occurs on an Oracle database.

Resolution

© 2023 Fusion5. All rights reserved.