The Lumary DC 2.5 release includes improvements for leave and rostering.
Follow this section to get a notification when we add new release notes.
Version 2.5
Available: 19 June 2025
This release includes improvements for leave, and rostering and scheduling.
Leave:
- support for multiple worker time zones for leave requests
- view the source of leave hours
- leave hover over displays leave periods, and
- leave editability improvements.
Rostering and scheduling:
The release also includes several bug fixes and other changes.
We’ve also included updates to permission sets.
Leave
Support for multiple worker time zones for leave requests
The leave hours calculated when a leave request is created or edited now support a workforce across multiple time zones. Previously, the leave hours were captured in the leave creating user’s time zone, and this could cause incorrect times being created on leave timesheet entries if the user that created the leave scheduled batch job was in a different time zone. Now, we store the worker’s time zone based on their user on the leave request, and utilise that to create the timesheet entries with the correct times.
View the source of leave hours
The Leave Hours Summary panel displayed on a leave record has been enhanced. It now displays and links the worker appointment, and whether it originated from a roster or the live schedule, for each leave period. This improvement allows roster planners to easily identify and investigate the origins of leave hours, ensuring compliance with entitlements.
Leave hover over displays leave periods
When hovering over leave in the roster period and live schedule calendars, roster planners can now view the leave hours that make up the leave. This enhancement ensures that leave hours contributing to payable and rostered hours are clearly visible.
Leave editability improvements
There have been significant improvements that enhance the ability to modify leave (including approved leave) to ensure the correct leave hours are sent to timesheets and payroll. A new Leave Request Item object has been introduced. Leave request item records represent the time and leave hours that the leave covers.
The scheduled job to process approved leave now runs four times a day and will process any leave request item records that have ended before the time of the batch running. This allows approved leave to be changed, such as the leave duration being shortened, provided it does not shorten past the current date.
This ensures that leave can be edited and the correct leave hours are sent to timesheets and payroll. Previously, all leave hours for the entire leave duration were sent when the first day of leave arrived.
Rostering and scheduling
View shifts and sessions together on calendars
We have introduced a new Shift & Session View setting on all calendars. This allows roster planners to see both shifts and sessions in a single view. This is the default view when shift functionality is enabled. On this view, sessions related to a shift are displayed below the shift, with a blue vertical line and indent.
Bug fixes and other changes
The following bug fixes and changes are also included in this release.
Workforce management
Worker appointment approval improvement - A minor update to the Worker Appointment tab, where we have removed standard Salesforce buttons. This allows the Process Worker Appointments button to be more prominent.
Rostering improvement - Schedulers can now complete sessions on behalf of workers with the Complete Session On Behalf custom permission added to the Lumary - Scheduling permission set. This enhancement ensures that shifts and sessions are finalised correctly, allowing for accurate worker payments and client charges.
Leave fixes:
- Resolved an issue where leave spanning across multiple days was only appearing for the first day of the leave in the calendar.
- A bug has been resolved where the leave hours were not considering the crossing of standard time into daylight savings time and vice versa. It will now calculate based on the hours that would have been worked (addition or reduction of an hour).
Worker contact fixes:
- Resolved an issue where the creation of a worker record did not populate the Worker Type field. This was required for worker processes to function correctly.
- We have removed redundant Primary Site and Secondary Site fields from the Worker page. Associated site records should be used instead.
Service delivery fix - An issue preventing the creation of service delivered records with travel and transport via the Service Delivery Entry screen has been fixed. This was caused by a validation rule that was ensuring that appointment travel records had an actual start date and an actual end date required for timesheets. However, the service delivered records created by the Service Delivery Entry screen do not have this information and do not populate it.
Award interpretation
Award interpretation improvements:
- The assignment record page has been updated. Previously, all related lists were under a single Related tab, and now we have included multiple tabs and related lists on the right-hand side of the page, which makes timesheets, assignment rates and more easily accessible.
- The Contracted Hours Start Date field has been added to the Worker Assignment page.
Assignment fix - An issue has been resolved where the Default Worker Assignment field on the worker record was not being populated during the Sync Assignments batch job. The fix ensures that only active assignments are synced, and the Default Worker Assignment field is correctly populated. We have updated the logic to determine the allocation of the default worker assignment as well:
- If there is only one assignment and it is active, assign that as the default assignment on the payee record and sync it across.
- If there are multiple assignments, but only one is active, then assign the active assignment as the default on the payee and sync it across.
- If there are multiple active assignments, leave the default on the payee blank. This will need to be manually chosen to sync the default worker assignment.
- If there are no active assignments, leave the default blank.
Cost code fix - We have addressed an issue with the standard cost code functionality where cost codes were not being captured and then not being created against timesheets. Additional permissions have been added for mobile workers (Lumary - Mobile User permission set) so that the cost code is correctly captured when they complete their shifts and sessions.
Transport fix - Validation logic has been updated to exclude transport entries from date validation checks, as they were only intended for travel. Previously, integration errors were incorrectly logged for transport records when the Actual Start Date field was blank, leading to their exclusion from timesheet processing. This update ensures that only travel entries are subject to date validation, allowing valid transport records to be processed correctly.
Permissions
Permission sets
We’ve made updates to field permissions on the permission set shown in the following table. If you have related custom or cloned permission sets we recommend that you add these permissions.
| Permission set | Apex Class |
|---|---|
| Lumary DC - Baseline | enrtcr__LeaveRequestProcessor |
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 | Associated Site | (Object Access) | Read |
| Contact | Read | ||
| Contact Status | Read | ||
| Primary Site | Read | ||
| Site | Read | ||
| Availability | Processed to Timesheet | Read, Edit | |
| Cancelled | Read, Edit | ||
| Start Date | Read, Edit | ||
| End Date | Read, Edit | ||
| Lumary - Mobile User | Worker Appointment | Cost Code | Read, Edit |
| Luamry WFM permission set | Custom permission |
|---|---|
| Lumary - Scheduling | Complete_Session_On_Behalf |
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 with updates.
To follow the section that contains this article:
- Click on the section link in the breadcrumb at the top of this page.
- 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. 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.