The Lumary DC 2.4 release includes improvements for client management, award interpretation, rostering and scheduling, and mobile.
Follow this section to get a notification when we add new release notes.
Version 2.4
Available: 20 May 2025
This release includes improvements for client management, award interpretation, rostering and scheduling, and mobile.
Client management:
Award interpretation:
Rostering and scheduling:
- cloning shifts
- shift completion travel and transport
- prevent editing of processed worker appointments
Mobile:
This release includes several bug fixes and other changes.
We’ve also included updates to permission sets and permission set groups.
Client management
Create an observation schedule for a high intensity need
We’ve enhanced the high intensity needs creation process to facilitate the streamlined development of an observation schedule. This enhancement ensures that related observations are captured, ensuring client’s receive the support they require.
Award interpretation
Display progress of manually triggered timesheet entries & items creation
In Release 2.3, we introduced a new button, Process Worker Appointments, on the Worker Appointment (WAP) list view that allows users to manually trigger the scheduled job for creating timesheet entries and items for completed and approved WAPs. Additionally, we have implemented a loading screen to inform users when the processing is complete, so they know when they can review the corresponding timesheets.
This functionality now requires that the user has the 2cloudnine Payroll Admin permission set.
Rostering and scheduling
Clone shifts to multiple days
We’re introducing the ability to allow users to clone shifts on the Base Roster and Roster Periods. Simply right-click on a shift, select Clone Shift and choose the days you want to replicate the shift to. Please note that only the shift and its associated worker appointment, session activities and assets will be cloned. Any sessions that are linked to the shift will not be cloned.
Desktop shift completion includes travel & transport
In Release 2.2, we introduced the ability for desktop users to complete a shift on the Scheduling Calendar. As part of this process, we have now introduced the ability to capture travel and transport information for the shift as well as any sessions linked to the shift.
Prevent editing of processed worker appointments
We’ve added a new validation rule to worker appointments to prevent editing the Finalised Start Date and Finalised End Date fields when it has been processed into a timesheet. This ensures that the worker appointment stays aligned with what has been processed into the timesheet.
Mobile for WFM
Allow workers to adjust shift clock in and out times
We have added a new Lumary Setting, Allow Workers to Adjust Shift Times. The setting toggles the ability for workers to edit the actual start and end date/times fields when concluding a shift on the mobile app.
By default, this setting is configured to false, which means that editing these fields is disabled.
Bug fixes and other changes
The following bug fixes and changes are also included in this release.
General
List view and action button improvements:
We’ve made updates to out-of-the-box list views, page layouts and action buttons designed to enhance usability, improve visibility of key information, and streamline navigation.
We have added fields to many of the standard Recently Viewed and All list views, ensuring relevant information is visible without the need to customize or click into individual records.
The set of action buttons on some layouts have been refined to present streamlined, task-relevant options only.
Service delivered permissions fixes - We have resolved a permission related issue affecting users on the Service Delivered Entry screen, which was preventing the page from loading for some users. For more details refer to the Permissions section.
Workforce management
Availability fixes - We have added a validation rule to ensure that a contact availability template record's Start Date is not before the related worker's Start Date.
Leave fixes - We have removed leave-specific fields for ad-hoc unavailabilities to reduce confusion when viewing the availability record.
Mobile fixes:
- Addressed an issue where workers were not able to view the employee message set by the scheduler for sessions in the mobile app.
- A bug has been resolved that previously restricted workers from logging their travel from unless they had already completed a travel to within the same session. This has now been updated, allowing workers to log travel from independently of whether travel to has occurred.
- Resolved an issue where the Prevent Multiple In Progress Sessions feature incorrectly prevented a worker from starting their next session due to multiple workers on the same session.
- We’ve added read access of the Restrictive Practice object to the Lumary Mobile - Frontline Mobile Only permission set so that mobile support workers can see a client’s restrictive practice records.
Session fixes - When cancelling a client using a billable cancellation reason, previously, only one planned service would have a cancellation service delivered record created. Now, each planned service outlined for the client will have a cancellation service delivered record created. There were also minor user experience improvements made to the cancellation process.
User set up console improvements - We have added some improvements to make the results of the User Set Up Console more consistent. These improvements include enforcing a phone number format of +61 followed by 12 characters, conditionally populating specific fields, and accurately filling in the street information on the worker's contact record.
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 DC - Service Delivery Management | Service Delivered | Case Note Title | Read, Edit |
| Lumary DC - Observation Management | Observation | Display Name | Read |
| Lumary DC - Case Note Management | Note Audit | Share via Client Portal | Read, Edit |
| Lumary - Mobile User | Observation | Case Note Title | Read, Edit |
| Note Audit | Share via Client Portal | Read, Edit |
WFM permissions
WFM permission sets extend some mobile, rostering and scheduling features. Updates to field permissions on these permission sets are shown in the following table. If you have custom or cloned permission sets that include these objects, we recommend that you add these permissions.
| Lumary WFM permission set | Object | Field | Permission |
|---|---|---|---|
| Lumary - Mobile User | Restrictive Practice | Authorisation Status | Read |
| Behaviour of Concern | Read | ||
| Behaviour Support Plan | Read | ||
| Client | Read | ||
| Client (Name) | Read | ||
| Description | Read | ||
| Duration | Read | ||
| Instructions | Read | ||
| Medication | Read | ||
| Other Behaviour of Concern | Read | ||
| Personal Support Plan | Read | ||
| PRN Medication | Read | ||
| Related Behaviour of Concern | Read | ||
| Restrictive Practice Type | Read | ||
| Schedule End Date / Time | Read | ||
| Schedule Start Date / Time | Read | ||
| Schedule Status | Read |
| Lumary WFM permission set | Apex class |
|---|---|
| Lumary - Award Interpretation | AWITimesheetEntriesBatchController |