You can download the full release notes as a PDF above for detailed information on all updates and fixes included in this version.

‍

If there are any post-install steps required, they will be listed below.

‍

‍

You can download the full release notes as a PDF above for detailed information on all updates and fixes included in this version.

‍

If there are any post-install steps required, they will be listed below.

‍

‍

Post Installation Steps

‍

OEM-930: Support at Home Statements

‍

The new fields included in this release are created automatically when the updated package version is installed. No manual field creation is required. The following steps must be completed manually by an administrator after installation.

‍

The new fields are not automatically added to Lightning Record Pages. Update the following pages in Setup → Lightning App Builder: maica_cc__Service_Agreement_Statement__c — Statement Line record page

‍

Add the following fields to the page layout component:

‍

1. Prior Period Line: maica_cc__Is_Prior_Period__c
2. Prior Period Budget Type: maica_cc__Prior_Period_Budget_Type__c
3. Total Claimable Expenditure: maica_cc__Total_Claimable_Services_Expenses__c

‍

maica_cc__Budget_Usage__c — Budget Usage record page

‍

Add the following field to the page layout component:

‍

1. Statement Line: maica_cc__Service_Agreement_Statement__c

‍

Additional Steps

‍

From this delta there are no new data migrations aimed at package upgrades. The change set is mostly Apex, LWC/Aura, metadata, and automation.Typical admin follow-up after deploy/upgrade:

‍

1. Permission sets / FLS — grant access to new fields (Resource, statements, funding item usage, etc.) and assign Maica_Overtime_Override where overtime override should be allowed.
2. Settings UI — review updated Travel (sequential travel, mechanism, gap hours, etc.), SaH / Aged Care sync (settingAgedCareSync), and NDIS sync options if you use them.
3. Flows — ensure the new SaH statements flow is active and wired into the intended process (per product design).
4. Data — sequential travel linkage fields are expected to be driven by runtime logic