Version 2.12
Available: 2 February 2026
The Lumary DC 2.12 release includes improvements for award interpretation, rostering and scheduling, leave, observations, incidents, smart file uploader, mobile and AR management.
Follow this section to get a notification when we add new release notes.
Award Interpretation:
Rostering and Scheduling:
Leave:
- session activities are retained when leave is approved, and
- cancel worker appointments prior to approving leave.
Observations:
- enteral feeding regime observations,
- menstruation observations, and
- skin integrity issue observations.
Incident ownership and notifications:
Smart File Uploader improvements:
- close superseded records,
- set client approved dates on service agreements, and
- migrate client files.
Viewing client files:
AR Management:
Salesforce Spring '26 updates:
New Lumary Academy features have been published since our last release.
The release also includes several bug fixes and other changes.
We’ve also included updates to profiles and permission sets.
Award Interpretation
Cost code support for worker leave
Cost code assignment on worker appointment records has been extended to also apply to worker leave. Administrators can enable and configure this feature under AWI Settings, to set a default cost code to be applied to all leave, or only to leave where there is no worker primary site cost code. This enhancement ensures that leave costs are accurately allocated for payroll and financial reporting.
On-call rostering
This release introduces support for after hours on-call rostering, enabled via a specialised roster type. Using an on-call roster facilitates and simplifies the process for managing who is rostered, and for workers to log calls, and receive payment for their allowance and remote work time, designed specifically to support the Remote Work clauses in SCHADS. On-call base roster session creation is automated using an out-of-the-box template and on-call roster periods feature automated validation, alerting users to any sessions that overlap with worker leave or use a weekday allowance on a public holiday, ensuring accurate and awards-compliant scheduling. On-call workers are not required to clock-in or out of on-call sessions except when one or more calls were received.
On-call workers can log calls received during their on-call shifts using a dedicated On-Call Log. This feature allows workers to record key details such as the reason for the call, how it was resolved, time of call, time of resolution, and escalation status, ensuring accurate records. Call logs are integrated with rostered on-call sessions to support award interpretation and payment for remote work performed as part of an on-call disturbance. Timesheet processing has been enhanced to ensure that workers are paid correctly for on-call allowance and disturbances, including the complex minimum engagement requirements detailed in the SCHADS award.
Future releases will add increased automation of on-call roster management and on-call call logging from Lumary mobile. Please be aware that the new roster cloning feature, also part of this release, is not supported for on-call type rosters.
Payroll reports
A new Pay Conditions report is available under Lumary - Award Interpretation reports folder, providing a detailed listing of interpretation rules and breakpoints. This report allows users to review key payroll settings, grouped by rule name and type, and listing applicable pay codes, multipliers, and thresholds.
We have added a suite of reports to assist with payroll go-live preparation and sign-off. These reports provide comprehensive visibility into assignments, payees, deductions, leave balances, and payroll compliance, supporting a smooth payroll go-live process. We also added leave reports for on-going monitoring and review of leave requests and balances.
Rostering and Scheduling
Cloning base rosters
We have introduced the ability to clone a base roster. When selecting the Clone button on a base roster, users will be prompted to populate the Roster Name, Roster Start Date, Is Active flag, Site, and Budget fields before confirming. The frequency cannot be edited and will remain the same as the base roster being cloned. All shifts, sessions, and contact availability templates will be cloned into the new base roster.
10-hour minimum break warning between shifts
When reviewing shift offers, there is now a check to ensure a minimum 10-hour rest break between a worker’s last shift, the offered shift, and their following scheduled shift. If a worker does not meet the minimum rest requirement, a warning is displayed, and the scheduler must confirm before proceeding with the assignment.
Leave
Session activities are retained when leave is approved
When leave is approved that overlaps with a worker's scheduled shift or session, the system automatically cancels them and creates a vacancy.
Previously, any shift and session activities scheduled originally were lost during this process. With this update, shift and session activities are now automatically copied to the vacancy, ensuring no activity information is lost when leave is approved. Users no longer need to manually re-add these activities to the vacancy.
The eligible shift and session activities that can be copied are paid breaks, unpaid breaks, and sleepovers. A setting controls whether all or specific activities are copied.
Cancel worker appointments prior to approving leave
Roster planners can now manually cancel worker appointments for leave that has not yet been approved, allowing them to promptly address shift coverage while awaiting manager approval. The Cancel Worker Appointments button is visible on the Availability record page.
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 cloned or custom 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.
Viewing client files
Viewing client files on Lumary Mobile
The Files related list on client records in the Lumary Mobile app has been updated to launch a new, streamlined component, making it easier for mobile users to view files. This component displays active client-related records with attached files. Users can view grouped files, see file details such as upload age and record type, and open file previews directly from the Files page. The component respects user permissions, ensuring only accessible records and files are shown, and includes options to filter the number of displayed records for a streamlined experience.
To enhance client information privacy within the mobile app, follow these steps to restrict mobile users from saving, sharing or printing files.
AR Management
Flexible invoice reminders
You can now prevent invoice reminders from being sent to specific debtors by using the new “Do Not Send Invoice Reminders” checkbox on both Account and Contact records. When this option is selected, invoice reminders will no longer be automatically sent for any invoices linked to that debtor (Contact or Account), giving you greater control over communications. “Do Not Send Invoice Reminders” can be managed via the Debtor Settings on the debtor (Contact or Account).
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.
See what's new in Lumary Academy
Check out our LIVE Lumary Academy updates page to stay across the latest improvements. Follow the page to stay in the loop and never miss an update.
Bug fixes and other changes
The following bug fixes and changes are also included in this release.
General
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.
Travel Non-Labour Expenses fix - Travel Non-Labour Expense Child Service Delivered records now correctly populate the Site Services/Program field based on a hierarchy of available matches, ensuring alignment with the parent service details. This issue only impacted Travel Non-Labour Expense Child Service Delivered records when the parent Service Delivered matched a Site Services/Programs, but the Provider travel - non-labour costs service did not have a corresponding Site Service Program record.
Award Interpretation
Expense claims fix - Approved worker expense claims are now processed seamlessly into payroll without requiring a second approval step.
Workforce Management
Leave fix - When creating leave via the Sick Call utility bar action, the success banner now includes a direct link to the newly created leave record. This allows schedulers to quickly access and review the leave details and any affected worker appointments. Additionally, the Sick Call screen will also reset the date fields to today’s date after leave creation, making it easier to enter subsequent records.
Mobile fix - When navigating within the mobile app, users were occasionally directed to the wrong page, most notably when tapping on a session. This has been resolved, ensuring users now navigate to the correct record pages throughout the app.
Rostered hours fixes - We have made significant refactoring improvements to how rostered and contracted hours are calculated and displayed throughout the system. Previously, various edge cases and complex scenarios could result in inaccurate hour calculations. These included misaligned start dates, unpaid time, multi-day sessions, and differing frequency cycles. This comprehensive update addresses the underlying calculation logic to ensure rostered and contracted hours are accurate across base rosters, roster periods, and scheduling views, regardless of roster configuration complexity. These improvements provide more reliable data for workforce planning and compliance tracking.
The following issues have been resolved as part of this update:
- When a shift or session includes unpaid time (e.g. unpaid breaks or sleepovers), the rostered hours now display correctly.
- The rostered hours displayed across the various calendar views will now correctly consider misalignments between dates displayed on the calendar and frequencies or dates on the worker assignment.
- When viewing 4-week base rosters with fortnightly worker assignments, rostered and contracted hours now display correctly in the 5-Day and 2-Day calendar views.
- When the base roster start date is in the past, the base roster now correctly displays contracted hours based on the next valid frequency cycle.
- When sessions or leave span multiple frequency cycles, rostered hours are now correctly allocated across cycles. This resolves issues, including negative values when sleepovers fall entirely within a subsequent cycle.
Rostering and Scheduling fixes:
- Overtime activities are now automatically removed from a session when it is linked to a shift using the New Shift Wizard. This ensures that overtime is only retained where appropriate, preventing outdated overtime records from remaining after sessions are associated with shifts.
- When creating or editing a Contact Availability Template, only workers are now shown in the Contact field, preventing clients and other contact types from appearing in the selection list. This update ensures users can only select and save active workers, making it easier to assign availability accurately and reducing the risk of errors.
- When adding clients to a session using the Modify Clients & Services right-click action, the list of available clients now automatically excludes anyone already added to the session, preventing duplicate client assignments.
Permissions
Profiles and permission sets
We’ve made updates to system permission for profiles shown in the following table. If you have custom or cloned profiles, we recommend that you add these permissions.
| Profile | System Permission | Access |
|---|---|---|
Lumary DC - Frontline User |
Send Custom Notifications |
Enabled |
| Lumary DC - Standard User | Send Custom Notifications |
Enabled |
| Lumary DC - System Administrator | Send Custom Notifications |
Enabled |
| Lumary Mobile - Frontline Mobile Only User | Send Custom Notifications |
Enabled |
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 - Mobile User | Hint and Tip Dismissal Log |
(Object Access) |
Create, Edit, Read |
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 AR - AR Management |
Account |
Do Not Send Invoice Reminders |
Read, Edit |
Contact |
Do Not Send Invoice Reminders |
Read, Edit |
|
Lumary DC - BSP Prescribing Practitioner |
Medication (Medication_Detail) |
Related Medication Name |
Read, Edit |
Lumary DC - Health Management |
Medication (Medication_Detail) | Related Medication Name | Read, Edit |
Lumary DC - Incident Capture and Management |
Reference Data |
Additional Notifications |
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 | ||
Site |
Area Manager |
Read | |
Team Leader |
Read | ||
Lumary DC - Mobile Baseline |
Goal Achievement Plan |
Plan Type |
Read |
Hint and Tip Dismissal Log |
(Object Access) |
Create, Edit, Read |
|
Tip ID |
Read, Edit |
||
Tip Page |
Read, Edit |
||
Tip Title |
Read, Edit |
||
User |
Read, Edit |
||
Lumary DC - 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 DC - Process Management |
Medication (Medication_Detail) |
Related Medication Name |
Read, Edit |
| Lumary DC - Roster Management | Contact Availability Template | Allocation Date | Read |
| Roster | Type | Read | |
Lumary DC - Set Up |
Reference Data |
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 |
Read, Edit |
| Permission Set | Apex Class |
|---|---|
Lumary - Mobile User |
enrtcr.UsageMetricsController |
Lumary DC - Baseline |
enrtcr.ClientFileMobileViewerController |
enrtcr.ClientFileMobileViewerHelper | |
enrtcr.ClientFileMobileVisibilitySelector | |
enrtcr.ContactRecordDeactivationController | |
enrtcr.ObservationRecordingAction | |
Lumary DC - Incident Capture and Management |
enrtcr.StringToCollectionConverter |
Lumary DC - Mobile Baseline |
enrtcr.ClientFileMobileViewerController |
enrtcr.ClientFileMobileViewerHelper | |
enrtcr.ClientFileMobileVisibilitySelector | |
enrtcr.ContactRecordDeactivationController | |
Lumary DC - Observation Management |
enrtcr.ObservationRecordingAction |
Lumary DC - Set Up |
enrtcr.NotificationConfigController |
enrtcr.StringToCollectionConverter |
| Permission Set | Custom Metadata Type |
|---|---|
Lumary DC - Baseline |
enrtcr.Client File Mobile Visibility |
WFM Permission sets
We’ve added new permission sets in this release.
| Permission set | Purpose |
|---|---|
| Lumary WFM - On-Call Management | For managers and administrators who oversee the on-call program (Payroll Officers, HR Managers, System Admins) |
| Lumary WFM - On-call Scheduling | For users who create and manage on-call rosters and sessions (Roster Coordinators, Workforce Planners) |
| Lumary WFM - On-call Worker | For workers who are rostered on-call and need to log incidents (Care Workers, Support Workers, Field Staff) |
We’ve made updates to field permissions on the permission set 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 - Scheduling | Contact Availability Template | Allocation Date | Read |
| Roster | Parent Roster | Read | |
| Type | Read, Edit | ||
| Session Type | Created Session Activity Category | Read |
Permission set groups
New permission sets have been added to the following permission set groups:
| Permission Set Group | Add Permission Set |
|---|---|
| Lumary DC - Business Owner | Lumary WFM - On-call management |
| Lumary DC - Regional Manager | Lumary WFM - On-call management |
| Lumary DC - System Administrator | Lumary WFM - On-call management |
| Lumary DC - Scheduler | Lumary WFM - On-call scheduler |
| Lumary DC - House Manager | Lumary WFM - On-call worker |
| Lumary DC - Team Leader | Lumary WFM - On-call worker |