> For the complete documentation index, see [llms.txt](https://knowledge.maica.com.au/maica-release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.maica.com.au/maica-release-notes/client-delivery/version-0.159.md).
# Version 0.159
Client Delivery V0.159 introduces one enhancement and a set of fixes. The headline change is improved stability of the Total Committed calculation for organisations with large data volumes. The fixes centre on Travel Management, correcting how travel Delivery Activities are created for group appointments with mixed funding types, how the travel percentage split is distributed across participants, and an error that could occur when saving travel with an empty kilometres value. The release also enforces required Participant Notes at check-out and ensures the mobile checklist save reports failures rather than reporting success, alongside general mobile app stability improvements.
{% hint style="warning" %}
This release has a required post-install step: the Total Committed batch must be re-scheduled after upgrading. See [Post-Install Steps](#post-install-steps) at the bottom of this page.
{% endhint %}
## Installation Information
Use the buttons below to install the latest version of **Maica Client Delivery** into the appropriate Salesforce org type. Select the link that matches your environment using the Buttons below.
{% hint style="info" %}
We always recommend installing the package into a **Sandbox** first to validate the release before deploying to **Production**. If you're unsure which option to select, please contact **Maica Support**.
{% endhint %}
**Production & Developer Edition Orgs**: Production URL
**Sandbox & Scratch Orgs:** Sandbox URL
{% hint style="success" %}
If you are on a Journey Agreement with us, your Account Manager will connect with you to organise the upgrade.
{% endhint %}
## At a glance
| Headline | Type | Area |
| ----------------------------------------------------------------------- | ----------- | ------------------ |
| **Improved Stability of the Total Committed Calculation at Scale** | Enhancement | Service Agreements |
| **Travel Delivery Activities Now Created Per Participant Funding Type** | Fix | Travel Management |
| **Travel Percentage Split Distributed Evenly Across Participants** | Fix | Travel Management |
| **Travel Management No Longer Errors on an Empty Kilometres Value** | Fix | Travel Management |
| **Required Participant Notes Enforced at Check-Out** | Fix | Appointments |
| **Mobile Checklist Save Reports Failures Instead of False Success** | Fix | Care Worker App |
| **General Mobile App Stability Improvements** | Fix | Care Worker App |
## Enhancements
### Improved Stability of the Total Committed Calculation at Scale
**Reference:** CC-698
We have improved the stability of the Total Committed calculation so that it completes reliably for organisations with large numbers of Agreement Items. Previously, on organisations with high data volumes, the calculation could fail when the volume of records to process exceeded platform processing limits.
**What's changed**
* The Total Committed calculation now processes records in a way that stays within platform processing limits, regardless of how many Agreement Items need to be calculated.
* Large updates are handled in stages so the calculation can complete on organisations with very high data volumes rather than failing partway through.
* Errors encountered while processing an individual record are recorded without halting the overall calculation, so a single problematic record no longer prevents the remaining records from being processed.
**Outcome**
The Total Committed calculation now runs to completion on organisations with large data volumes, where it could previously fail, and the resulting Total Committed values on Agreement Items are updated consistently.
**Example scenarios**
* ✅ An organisation with a very large number of Agreement Items runs the Total Committed calculation → the calculation completes successfully across all records.
* ✅ A single record cannot be processed → the issue is logged and the remaining records are still calculated and updated.
***
## Fixes
### Travel Delivery Activities Now Created Per Participant Funding Type
**Reference:** CC-709
We have corrected how travel Delivery Activities are created for group appointments whose participants have different funding types. Travel Delivery Activities are now evaluated for each participant individually against their own funding type, so a participant whose funding type is not mapped for travel no longer receives a travel Delivery Activity.
**What was fixed**
* The travel Appointment Service is now resolved per participant, based on that individual participant's funding type, rather than from a single combined set of all participants' funding types.
* A Non-Time Based or Time Based travel Delivery Activity is only created for a participant when their funding type resolves to a valid travel Appointment Service in the Cost Management settings.
* Participants whose funding type is mapped as **Not Applicable**, or has no mapping, are skipped and no travel Delivery Activity is created for them.
**Outcome**
In a group appointment containing participants on different funding arrangements, each participant now receives travel Delivery Activities only where their funding type is configured for travel, preventing travel charges from being raised against participants who should not receive them.
**Example scenarios**
* ✅ A group appointment has one Plan Managed participant and one Fee for Service participant whose funding type is mapped as Not Applicable → only the Plan Managed participant receives a travel Delivery Activity.
* ✅ All participants in an appointment have funding types mapped for travel → each participant receives their travel Delivery Activities as expected.
* ✅ A participant has no travel mapping for their funding type → no travel Delivery Activity is created for that participant, and other participants are unaffected.
***
### Travel Percentage Split Distributed Evenly Across Participants
**Reference:** CC-720
We have corrected how the travel percentage is split across participants when the number of participants does not divide evenly into 100. The remainder is now distributed evenly across participants rather than being applied entirely to the first participant.
**What was fixed**
* The travel percentage is now distributed as evenly as possible across all participants, with any remainder spread one increment at a time across participants rather than added in full to the first participant.
* The split now uses fractional percentages, so participant shares are balanced rather than skewed by whole-number rounding.
**Outcome**
Travel costs are now shared evenly across participants in a group appointment. For example, an appointment with six participants now produces balanced shares close to an even split, rather than allocating a disproportionate share to the first participant.
**Example scenarios**
* ✅ A group appointment has six participants → travel is split into balanced shares across all six, rather than allocating an oversized share to the first participant.
* ✅ A group appointment has a participant count that divides evenly into 100 → each participant receives an equal share, unchanged from before.
* ✅ A group appointment has a participant count that does not divide evenly → the small remainder is spread across participants one increment at a time.
***
### Travel Management No Longer Errors on an Empty Kilometres Value
**Reference:** CC-718
We have resolved an error that could occur in the Travel Management tool when a kilometres proportion value was left empty. The tool now treats an empty or invalid kilometres value as zero, so the travel record saves without error.
**What was fixed**
* An empty or invalid kilometres proportion entered in the Travel Management tool is now treated as zero before the travel record is saved.
* This prevents the "Invalid decimal: NaN" error that previously occurred when the value was submitted.
**Example scenarios**
* ✅ A user opens the Travel Management tool and leaves the kilometres proportion empty → the value is treated as zero and the travel record saves successfully.
* ✅ A user enters a valid kilometres proportion → the entered value is used as expected.
***
### Required Participant Notes Enforced at Check-Out
**Reference:** CC-715
We have ensured that required Participant Notes are enforced when checking out of an appointment. Where Participant Notes are required, a check-out can no longer be completed until a note has been entered.
**What was fixed**
* When Participant Notes are required, attempting to check out without entering a note is now blocked, and the user is advised that Participant Notes are required before checking out.
* The requirement is enforced at the point of check-out, so a check-out cannot be completed with the note left blank.
**Example scenarios**
* ✅ Participant Notes are required and a user attempts to check out without entering a note → the check-out is blocked and the user is prompted to enter the required note.
* ✅ Participant Notes are required and a user enters a note before checking out → the check-out completes successfully.
* ✅ Participant Notes are not required → check-out behaviour is unchanged.
***
### Mobile Checklist Save Reports Failures Instead of False Success
**Reference:** CC-723
We have corrected the behaviour of the checklist save in the Care Worker mobile app so that a failed save is reported to the user rather than appearing to succeed. Previously, a save that failed could still report success, leaving checklist changes unsaved without the user being aware.
**What was fixed**
* A checklist save that does not complete successfully now surfaces the failure to the user instead of reporting success.
* Checklist changes that have not been saved are no longer presented as though they were saved.
**Example scenarios**
* ✅ A checklist save completes successfully → the user sees a success result and the changes are saved.
* ✅ A checklist save fails → the user is informed the save did not complete, rather than seeing a false success.
***
### General Mobile App Stability Improvements
**Reference:** CC-724
We have made general stability improvements to the Care Worker mobile app to address an issue that could affect loading of the app. These changes improve the reliability and consistency of the mobile experience.
***
## Post-Install Steps
### Required
{% hint style="warning" %}
Scheduled Apex jobs do not survive a package install or upgrade. This step must be completed in every org after upgrading to this version, otherwise future and committed values will not be projected.
{% endhint %}
{% stepper %}
{% step %}
#### Re-schedule the Total Committed batch
After installing or upgrading to this version, re-schedule the Total Committed batch in **Maica Settings → Scheduled Jobs**. Because scheduled Apex jobs are not retained through a package install or upgrade, this must be set up again per org. Without it, future and committed values will not be projected.
{% endstep %}
{% endstepper %}
### Recommended Checks
These checks are optional but recommended after upgrading.
{% stepper %}
{% step %}
#### Review travel configuration
Travel Delivery Activity resolution is now performed per participant by funding type. Confirm that your Non-Time Based Cost Management mapping covers every funding type used in group appointments, so that travel is created correctly for each participant.
{% endstep %}
{% step %}
#### Confirm check-out notes configuration
Check-out will now block where Participant Notes are required. Before rollout, confirm the "require notes at check-out" configuration is set where you expect it, so the newly enforced rule does not surprise field staff.
{% endstep %}
{% step %}
#### Re-test the mobile app
No configuration is required for the mobile changes, but it is recommended to re-test mobile check-out and checklist save after upgrading.
{% endstep %}
{% endstepper %}