The Lumary DC 2.3 release includes improvements for award interpretation, goals, house rosters, rosters and mobile.
Follow this section to get a notification when we add new release notes.
Available: 23 April 2025
This release includes improvements for award interpretation, goals, house rosters, rosters and mobile.
Award interpretation:
Goals:
House rosters:
Mobile:
Rosters:
The release also includes several bug fixes and other changes.
We’ve also included updates to permission sets and profiles.
Award interpretation
Manually trigger timesheet entries & items creation
We have added a button on the worker appointment (WAP) listview labelled 'Process Worker Appointments'. This button will run the AWITimesheetEntriesBatch job, which will process approved WAPs into timesheet entries and items. This allows a provider to ensure that all approved WAPs have been processed before approving timesheets and creating a pay batch or running payroll.
Goals
Streamlined goal planning
We've simplified the process of creating Agreed Service Goals with the following improvements:
- Users are now presented with dropdown menus when selecting the appropriate NDIS Goal and Goal Category.
- Both the Actions and Strategies and Barriers to Success fields have increased character limits.
- The Date Achieved field now appears if the Status selected is ‘Achieved’.
- When the Review Status is set to either ‘In Progress’ or ‘Complete,’ the fields for Goal Outcome Review and Evidence to Support Outcome will now be displayed.
This improvement reduces confusion and enhances the usability of the feature, making goal planning more intuitive.
House rosters
Required workers needed to support the house roster
As part of this release, we have introduced the ability to view the required number of workers needed to support the clients on the house roster. This feature contains the following parts to be enabled correctly.
Setting a shared support on a session - We have introduced the ability to set a shared support ratio on the session with the Work Type of ‘Accommodation’ on the roster. The fields ‘Worker Ratio’ and ‘Client Ratio’ will appear under the ‘Attendees’ section to be populated accordingly.
Displaying shared supports on the house rosters - In accordance with the changes above, we have introduced the ability to view shared supports on the house roster. Previously, the gaps in between community participation, employment supports, absences and individual supports were assumed to be shared supports. However, with some feedback, we have made these visible with clear ratios to distinguish between the already shown individual supports and other times the client is outside of the house.
These shared supports will be present in the lane of the corresponding client they belong. The shared supports will be displayed similarly to how the individual supports are shown, with the following details:
- Ratio (e.g. 1:4)
- Duration (in hours)
- If the duration is less than or equal to 30 minutes, only the ratio will be shown.
- Start Time
- End Time
The displayed ratio is based on either the values set on the Worker Ratio and Client Ratio fields, or if these are not populated on the session, then the displayed ratio will be one worker to support all clients that appear on the house roster.
When hovering over the shared support a pop-up will also appear, which will display the following information:
- Client’s Name
- Start Time
- End Time
- Duration (in hours)
The shared supports will also be updated based on changes made on the House Roster. This includes:
- Via the toggles on the submission (e.g. enabling ‘Show In-Progress Submissions’).
- Via the ‘Modify Session Times’ functionality on the submission.
Printing the house roster (via the print icon) will now include the shared supports, similar to how the individual supports are displayed.
Displaying the required worker count on the house roster - On the house rosters we now provide an indicator to show the number of workers required to provide sufficient support for a client’s needs during a session. As the number of workers or the amount of support required fluctuates during the period of the session, the house roster will have indicators that will reflect these changes accordingly as well.
These will be displayed on the house roster as a new lane underneath the Worker Appointment(s) called Required Worker(s).
Each indicator that represents the required worker count will be presented in a fractional format. In this format, the numerator signifies the number of workers assigned for the session, while the denominator illustrates the total number of workers necessary to effectively support the client during that session. Both figures will be represented in decimal format, rounded to the nearest tenth. This ensures enough precision is provided so that house managers can make informed decisions when deciding where to allocate resources for the house.
The indicator will show green when the number of workers is sufficient to support the client's requirements. If there are not enough workers, the indicator will change to red.
The required worker count will also update depending on changes to the house roster, this can include:
- Adding additional workers to a particular Session.
- Toggling the filters using the filter button.
- Changing the week currently being displayed.
- Modifying the Session on the House Roster of the Submission.
Improved house roster filtering
For this release, we have enhanced the house rosters to now display the roster it is associated to at the top for improved clarity. Additionally, we have also improved the logic on the house roster to determine which roster to utilise. The criteria for selecting the appropriate roster is:
- The roster must be active.
- The roster site must match the proposed house site.
- The roster with the most recent start date.
- If the roster's start date is the same, it will default to using the most recent created date instead.
Mobile
Travel to and travel from
Previously, when completing a shift with sessions in the mobile app, the shift allowed for travel to and travel from, however, the sessions only allowed for transport. In this release, sessions related to a shift will now also allow for travel to and travel from, which extends coverage of all scenarios. Please note that this functionality will still respect the Hide Travel To and Hide Travel From settings.
Rosters
Display session type name
Hovering over a session in any of the rostering calendars will now display the session type.
Bug fixes and other changes
The following bug fixes and changes are also included in this release:
Calendar fixes:
- We have resolved an issue that caused the calendar to fail loading when more than 999 workers were associated with a single public holiday calendar record.
- A bug has been resolved with the calculation of the scheduled displayed in the calendars. It was previously reducing the scheduled hours by sleepover and unpaid activities, however, it was also incorrectly including the hours for cancelled Worker Appointments. This error resulted in scheduled hours appearing as negative in certain cases.
Roster fixes:
- We addressed an issue where the Services tab was being skipped in when using the Session Wizard in the Scheduling Calendar.
- We resolved a bug that stopped the pre-population of the Start Date/Time and End Date/Time fields (with the worker appointment’s date/times) during the creation of session activities.
-
We have introduced two new validation rules for the Appointment Travel object to ensure that entries are correct:
-
Actual Start Date and Actual End Date must be populated upon completion for Timesheet Entry creation, and
-
the Actual Start Date must precede the Actual End Date.
-
Leave fix - We have fixed an issue that was preventing users from changing the leave type when editing or creating a leave request.
Lumary settings improvements:
We’ve made a change to the default out-of-the-box values for two Lumary settings:
- Worker Appointment Approve Tolerance = 15
- Include Live Sessions in Leave = Part Time
This was done based on customer experience, with these being the most common setting values. If these settings have values already, they will not be overridden.
Mobile fixes:
- We have added the Lumary Mobile Home tab to the Lumary Mobile - Frontline Mobile Only User profile. This tab permission was granted by the Lumary - Mobile User permission set however, this was done to the profile to guarantee mobile Users have the necessary access.
- Support worker users with the Lumary Mobile - Frontline Mobile Only User profile and the Lumary Mobile- Frontline Mobile Only permission set group were unable to see client alerts when viewing a session in the mobile app. This has now been resolved by provisioning further alert access.
- A bug was identified where the initial transport trip does not accurately estimate the distance transported (and shows 0), while subsequent trips function correctly. This issue has been corrected.
Region fix - In a previous release, we adjusted the management of regions to ensure that regions are now represented as Reference Data with a record type of Session Region. As part of this release, we have removed the old references to the now deprecated Region object and have aligned correctly to use the Reference Data version moving forward, this includes references on the Worker, Waitlists and the 'Quick Add Enquiry to Waitlist' action on the Enquiry.
Shift improvements:
- This was done based on customer experience, with these being the most common setting values. If these settings have values already, they will not be overridden.
- If shift functionality is disabled (the Lumary setting 'Enable Shift Functionality' is set to false), the Shift tab when viewing a Session record page will no longer be visible.
- We have made stability improvements to the Complete Shift process on the desktop.
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 - Mobile User | Alert | Care Plan Item | Read |
| Creation Details | Read | ||
| Lumary DC - Enquiry Management | Waitlist | Session Region | Read, Edit |
| Lumary DC - Waitlist Management | Reference Data | Cost Centre | Read |
| Description | Read | ||
| GL Code | Read | ||
| Group Id | Read | ||
| (Object Access) | Read | ||
| (Record Type) Session Region | Visible | ||
| Waitlist | Session Region | Read, Edit | |
| Lumary DC - Worker Management | Reference Data | Cost Centre | Read |
| Description | Read | ||
| GL Code | Read | ||
| Group Id | Read | ||
| (Object Access) | Read | ||
| (Record Type) Session Region | Visible | ||
| Waitlist | Session Region | Read, Edit |
| Permission set | Apex classes |
|---|---|
| Lumary DC - Baseline | AgreedServiceGoalController |
| GoalPlanClientController |
Profiles
We’ve made updates to the permissions and page layout assignments included in the profiles shown in the following table. If you have custom or cloned profiles, we recommend that you add them.
| Profile | Object | Permission |
|---|---|---|
| Lumary Mobile - Frontline Mobile Only User | Lumary Mobile Home (tab) | Default On |
Follow us to get update notifications
If you'd like to receive email alerts when new release notes are added to this section:
- Go to the Lumary DC releases section.
- Click on the Follow button.
- Select New Articles.
A message will appear confirming that you are now following this section. The system will send you an unstyled version of new or updated pages. You can cancel these notifications at any time by clicking on Unfollow.
Users can only follow sections on Lumary's Help Centre, rather than individual articles. This means you'll get email notifications whenever a new article is published in this section, or when an article is republished.