---
url: "https://www.skedulo.com/release-notes/skedulo-healthcare-employment-hero-v3-1"
type: "releaseNote"
title: "AU Healthcare + Employment Hero Integration v3.1 is now available"
version: "v3.1"
date: "2025-01-23"
---

# AU Healthcare + Employment Hero Integration v3.1 is now available

Includes enhancements to merge shift logic and setting KM Travelled field upon generating Shifts.

**Important**

_When upgrading to this version, if you have skipped any previous releases, please use the installation links below to proceed as usual. However, we recommend reviewing the release notes for the skipped versions to familiarise yourself with new features, issue fixes, and to ensure compatibility and correct setting requirements._

**Compatibility**

This package version requires the following mandatory packages in place before installation.

- **Skedulo Core Package:** 102.56+
- **Lumary:** 20.3.9+
- **Skedulo AU Healthcare:** 1.209+

**Important** – There are upgrades in the package compatibility compared to the last release. Please carefully follow the above before the installation.

**What’s New**

**Enhancements to Merge Shift Logic**

- Currently shifts are merged when jobs have the same Work Type, with the pre-condition that the setting KP_Allow_To_Merge_Shifts is set to “True”.
- A few enhancements have been introduced to accommodate other needs:
- New setting **KP_Disable_Merge_Shifts** (Setup > Custom Settings > Skedulo Configs) can be used to disable the merge shift functionality as a whole:
- Value: True/False
- Default value: False – to keep the current state as is for all customers (merge shift logic is still active)
- New settings **KP_Enable_Merge_Shifts_With_Conditions** and **KP_Fields_To_Merge_Shifts **(Setup > Custom Settings > Skedulo Configs) can be used in case the jobs need to have other matching values in order to merge shifts, rather than just Work Type:
- For example:
- In order to merge shifts, the jobs need to have the same values of Work Type and Cost Code.
- Enable the setting **KP_Enable_Merge_Shifts_With_Conditions** to “True”. And input the field name(s) to the value of **KP_Fields_To_Merge_Shifts** “skedkp__Work_Type__c, skedhealthcare__Cost_Centre__c”
- Now shifts will only merge if the back-to-back jobs have the same values of Work Type and Cost Code.
- The new setting **KP_Enable_Merge_Shifts_With_Conditions **should have the default value as “False” meaning the current merge shift logic will remain as is where it refers to the existing setting KP_Allow_To_Merge_Shifts and merges shift when only Work Type is matching.
- In order to merge shifts, the jobs need to have the same values of Work Type and Cost Code.
- Enable the setting **KP_Enable_Merge_Shifts_With_Conditions** to “True”. And input the field name(s) to the value of **KP_Fields_To_Merge_Shifts** “skedkp__Work_Type__c, skedhealthcare__Cost_Centre__c”
- Now shifts will only merge if the back-to-back jobs have the same values of Work Type and Cost Code.
- Value: True/False
- Default value: False – to keep the current state as is for all customers (merge shift logic is still active)
- For example:
- In order to merge shifts, the jobs need to have the same values of Work Type and Cost Code.
- Enable the setting **KP_Enable_Merge_Shifts_With_Conditions** to “True”. And input the field name(s) to the value of **KP_Fields_To_Merge_Shifts** “skedkp__Work_Type__c, skedhealthcare__Cost_Centre__c”
- Now shifts will only merge if the back-to-back jobs have the same values of Work Type and Cost Code.
- The new setting **KP_Enable_Merge_Shifts_With_Conditions **should have the default value as “False” meaning the current merge shift logic will remain as is where it refers to the existing setting KP_Allow_To_Merge_Shifts and merges shift when only Work Type is matching.
- In order to merge shifts, the jobs need to have the same values of Work Type and Cost Code.
- Enable the setting **KP_Enable_Merge_Shifts_With_Conditions** to “True”. And input the field name(s) to the value of **KP_Fields_To_Merge_Shifts** “skedkp__Work_Type__c, skedhealthcare__Cost_Centre__c”
- Now shifts will only merge if the back-to-back jobs have the same values of Work Type and Cost Code.

**Enhancements to setting KP_JA_Summed_Travel_Km_Fields**

- The setting **KP_JA_Summed_Travel_Km_Fields **is used to specify the field(s) on the Job Allocation object whereby the system will sum their values when calculating the Kilometer Travelled field upon generating Shifts.

![Image](https://www.skedulo.com/wp-content/uploads/2025/06/Skedulo-Healthcare-Employment-Hero-V3.1-image-1.png)

![Image](https://www.skedulo.com/wp-content/uploads/2025/06/Skedulo-Healthcare-Employment-Hero-V3.1-image-2.png)

![Image](https://www.skedulo.com/wp-content/uploads/2025/06/Skedulo-Healthcare-Employment-Hero-V3.1-image-3.png)

- This setting was fixed to only support three fields:
- skedhealthcare__Est_Distance_Traveled_KM__c;
- skedhealthcare__Total_Km_Travelled_with_Client__c;
- skedhealthcare__Actual_Distance_Traveled_KM__c
- This has now been enhanced to configure any other fields from the Job Allocation object.