The Lumary AC 2.12 release includes improvements for DEX Extracts, Observations, Incident Management, Smart file uploader and fixes several bugs.
Follow this section to get a notification when we add new release notes.
Version 2.12
Available: 2 February 2026
This release includes enabling reporting MAC ID in DEX Extract, enhancements for observations, flexible incident management ownership & notifications, smart file uploader improvements and fixes several bugs.
DEX Extract:
Observations:
Incident ownership and notifications:
Smart file uploader:
Salesforce Spring '26 updates:
The release also includes several bug fixes and other changes.
We’ve also included updates to permission sets.
DEX Extract
Reporting of MAC ID in DEX Extract
Functionality has been added to DEX Extracts to support providers that are now required to capture whether a client is registered for My Aged Care (MAC) and their unique My Aged Care Id, as part of Commonwealth Home Support Program (CHSP) reporting requirements.
To enable this reporting Provider’s can add the HASMACID to the DEX Activity Specific Requirements on the Rate Type.
Once the DEX Activity Specific Requirements includes HASMACID, clients with a My Aged Care Number in Lumary will now have this data available in the DEX Extract. To view the new XML fields RegisteredForMAC and MacId under the Client Node check out our DEX XML mapping to CM fields and objects article.
Validation has also been added to ensure that when the DEX Activity Specific Requirements include HASMACID, a valid My Aged Care (MAC) Number must be provided for the client. The MAC Number must start with 'AC' and contain exactly eight numerical digits. If this information is missing or incorrectly formatted, users will receive a clear error message during the extract process. Ensuring providers are meeting upcoming mandatory reporting requirements.
Observations
Enteral Feeding Regime observations
- We’ve introduced a new checkbox users can tick to indicate a continuous feed is occurring when capturing Enteral Feeding Regime observations.
- If this checkbox is ticked, new fields for Feed Start Date/Time and Feed End Date/Time are displayed.
- A new Rate (mL/hr) field has also been added to record the feed rate in mL per hour.
- The Latest Observations card and Last Observations list now display relevant values, providing clearer tracking for each observation.
Menstruation observations
- The Menstruation record type has been enhanced to include new fields for capturing Cycle Stage, Period Duration (days), Other Symptoms, and Additional Information.
- There are also updated Amount options to record more meaningful information relating to the client’s flow.
- The Latest Observations card and Last Observations list now display relevant values, making it easier to track detailed information about a client’s menstrual cycle, and improving the accuracy and usefulness of observation records.
Skin Integrity Issue observations
- We’ve improved the Skin Integrity Issue record type in Observations by adding a new field to record the Area/s for the location of the issue. If users select a Location of “Other”, they can now record specific information in the new Other Location field.
- Picklist options for the Estimated Size or Scale field have been refined to include “<1cm” and “>12cm”, and no longer include the option for “Other”.
- A new checkbox is now available to indicate when an incident has been recorded in relation to the observation.
- Additional options are available in the Possible Cause list. If users select a Possible Cause of “Other”, they can now record specific information in the new Other Possible Cause field.
- The Integrity Issues option of Pressure Sore has been relabelled to Pressure Injury.
- The Latest Observations card and Last Observations list now display relevant values, providing a more informative experience when viewing skin integrity observations.
These changes make it easier record and review observations across both desktop and mobile, and ensure more accurate record-keeping.
Incident ownership and notifications
New incident ownership and notifications feature
We’ve introduced new Incident Management ownership and notification features to make it easier to configure, manage, and automate how incidents are assigned and communicated across your organisation. When enabled, incident ownership is automatically assigned on creation based on the incident’s type and sub-type, with new incident notifications sent according to your configuration.
Key highlights:
- A new Incident Management Settings screen provides a central place to manage incident ownership and notification rules.
- Automated incident assignment ensures incidents are routed to the correct owner for both site-related and non-site-related incidents.
- Email and bell notifications are sent based on your setup.
- Incident owners receive email notifications when ownership of open incidents is reassigned, including a direct link to the record.
- Flexible override options allow ownership and additional notifications to be configured by incident type and sub-type, with support for users, groups, roles, and queues.
- A new default Incident Management Queue ensures incidents are always assigned when no specific configuration is found.
- Improved visibility with the Owner field added to Incident record page, and the Site field displayed when applicable.
- If this feature is disabled, incident ownership will remain as the submitter, or according to any other ownership customisations you may have in your environment.
These enhancements simplify configuration and provide a more consistent, transparent incident management experience. Find out more about managing incident ownership and notifications.
To use this feature you must follow the steps below for any profiles your organisation has assigned to users submitting incidents:
To enable sending custom notifications on profiles
Click on the setup cog icon and select Setup.
Click in the Quick Find search field.
Type profiles.
Click on the Profiles text link.
Click on the text link of a profile being used by users that submit incidents in your organisation.
Scroll down and click on System Permissions.
Click Edit.
Scroll down and tick the box for Send Custom Notifications.
Click Save.
Repeat steps 4-9 for all other profiles assigned to users that submit incidents in your organisation.
Smart file uploader improvements
Close superseded records
When creating new records using the smart file uploader, users are now prompted to close off any existing records that may be superseded by the new upload. After uploading a file, if relevant active records exist, a window will appear allowing users to select and mark these as inactive, streamlining record management and reducing manual effort. Users can skip this step if no records need to be closed, and a confirmation message will display for any records updated. This enhancement improves efficiency and ensures records remain up to date without extra navigation.
Set client approved dates on service agreements
When uploading files for Service Agreements using the smart file uploader, users will now be prompted to enter a Client Approved Date if the agreement is in “Current” or “Quote Submitted” status and the date is not already set. Users can choose to accept the default date, enter a different date, or skip updating the date if preferred.
Migrate client files
A new Migrate Client File action button is now available on the Client page layout. This feature allows users to easily move files that are currently linked directly to a client record and associate them with the appropriate related record instead. This makes it easier to organise and locate client files and ensures they are linked to the correct records, rather than remaining on the contact.
Find out more about these improvements when adding and storing files on a client's record.
If your organisation uses custom page layouts or custom Lightning record pages for client records, you can add this button to your layouts by following the guidance below:
To update a custom page layout
Click on the cog setup icon.
Select Setup.
Click on the Object Manager tab.
Click in the Quick Find search field.
Type Contact.
Click on the text link of the Contact object name.
Click on Page Layouts.
Click on the text link of the custom Page Layout you are using, e.g:
Cloned Client Layout.From the top palette, select Mobile and Lightning Actions and click and drag the Migrate a client file action to the Salesforce Mobile and Lightning Experience Action section, and drop it in the desired location.
Click Save
To update a Lightning record page
Click on the cog setup icon.
Select Setup.
Click on the Object Manager tab.
Click in the Quick Find search field.
Type Contact.
Click on the text link of the Contact object name.
Click on Lightning Record Pages.
Click on the text link of the custom Lightning record page you are using, e.g:
Cloned Client Lightning Record Page.Click on the Edit button.
Click on the Highlights Panel section at the top of the layout.
In the right-hand pane scroll down and click Add Action button.
Find and select Migrate a client file in the Actions search field.
Click Done.
Click Save.
Salesforce Spring '26 updates
List view sorting
Blank or empty values in list views appear at the bottom when sorting in ascending order (previously appeared at top). Please be aware that if you have any custom or private list views where you expect blank values to appear first, they will now appear last when sorting in ascending order. This change will reflect in your environment when the Salesforce Spring '26 upgrade is deployed, likely the weekend of February 21st 2026.
SAML Single Sign-On migration
If your organisation uses SAML for single sign-on (SSO), you must migrate to the multiple-configuration SAML framework before the Salesforce Summer '26 release to prevent SSO login disruptions. Check Setup → Release Updates to see if this applies to your environment.
Bug fixes and other changes
The following bug fixes and changes are also included in this release.
General
Case Notes improvement - When creating a Case Note using a template with Care Management Capture enabled the Bill Care Management Funding toggle will now default to ON. This change streamlines the workflow for frontline staff and reduces the risk of missing Care Management minute capture, while users can still turn the toggle off if needed.
Observations fix - When multiple observation schedules are recorded for the same observation type for a client, captured observations are now linked to the correct Latest Observation card for the schedule. Previously, observations were always being displayed on the first schedule’s card for the observation type. This update ensures that each observation is shown on the appropriate card, improving clarity for users.
SAH Extract Invoice results fix - We've resolved an issue that caused an error when processing SAH invoice results CSV files with fewer than 51 rows.
Payment statement upload fix - You can now upload Payment Statement files for claims when the Reduction Type column is missing or only partially populated. This update ensures that files without the Reduction Type column will process successfully without error.
Permissions
Permission sets
We’ve made updates to field permissions on the permission sets shown in the following table. If you have custom or cloned permission sets that include these objects, we recommend that you add these permissions.
| Permission set | Object | Field | Permission |
|---|---|---|---|
| Lumary - Extracts | Extract Item | My Aged Care Id | Read, Edit |
| Registered for MAC | Read, Edit | ||
| Lumary AC - Goal Management | Goal Achievement Plan | Plan Type | Read |
| Lumary AC - Health Management | Medication (Medication_Detail__c) | Related Medication Name | Read |
| Lumary AC - Incident Capture and Management | Reference Data | Additional Notifications | Read |
| Area Manager | Read | ||
| Non-Site Related Owner | Read | ||
| Non-Site Related Owner Specific Id | Read | ||
| Notification Public Groups | Read | ||
| Notification Specific Users | Read | ||
| Site Related Owner | Read | ||
| Site Related Owner Specific Id | Read | ||
| Team Leader | Read | ||
| Lumary AC - Observation Management | Observation | Area | Read, Edit |
| Cycle Stage | Read, Edit | ||
| End Date/Time | Read, Edit | ||
| Has an incident been recorded | Read, Edit | ||
| Other Location | Read, Edit | ||
| Other Possible Cause | Read, Edit | ||
| Other Symptoms | Read, Edit | ||
| Period Duration (days) | Read, Edit | ||
| Rate (mL/hr) | Read, Edit | ||
| Start Date/Time | Read, Edit | ||
| Lumary AC - Process Management | Medication (Medication_Detail__c) | Related Medication Name | Read |
| Lumary AC - Set Up |
|
Additional Notifications | Read, Edit |
| Non-Site Related Owner | Read, Edit | ||
| Non-Site Related Owner Specific Id | Read, Edit | ||
| Notification Public Groups | Read, Edit | ||
| Notification Specific Users | Read, Edit | ||
| Site Related Owner | Read, Edit | ||
| Site Related Owner Specific Id | Read, Edit | ||
| (Record Type) Incident Metadata | Visible |
| Permission set | Apex Class |
|---|---|
| Lumary AC - Baseline | enrtcr.ContactRecordDeactivationController |
enrtcr.ObservationRecordingAction | |
| Lumary AC - Incident Capture and Management | enrtcr.StringToCollectionConverter |
| Lumary AC - Set Up | enrtcr.StringToCollectionConverter |
enrtcr.NotificationConfigController |
| Permission set | Tab | Permission |
|---|---|---|
| Lumary AC - Set Up | Incident Management Settings | Visible |
Follow us to get update notifications
You can follow sections in Lumary's Help Centre with your Help Centre account. If you follow a section, you'll receive email notifications whenever a new article is published in that section, or when an article is republished.
To follow the section that contains this article:
- Go to the Releases section. This section currently appears under Lumary AC Releases > Releases.
- Click on the Follow button.
- If you're not already logged in, you'll be prompted to log into the Help Centre. You'll need a Help Centre account.
- Select New Articles.
- A message will appear confirming that you are now following this section and the label on the button will change to Following. The system will send you an unstyled version of new or updated pages.
You can cancel these notifications at any time by:
- using the link at the end of the email, or
- going to the Releases section and clicking on Unfollow.