Version 2.18
Available: 21 July 2026
The Lumary DC 2.18 release includes improvements for award interpretation, case notes, engagement console, observations tracking, rostering and more.
Follow this section to get a notification when we add new release notes.
Required packages
Lumary CM 26.0.1
Lumary AWI 2.18 and dependencies
Lumary Base 2.4
Award interpretation:
Case notes:
Lumary engagement console:
Observations tracking:
Funding Period Enhancements:
- edit individual period amounts independently
- modify period start and end dates
- prior period rollover transparency, and
- enhanced funding period visibility.
NDIS July 2026 price guide changes:
Travel & Transport budgeting and billing:
Updates for DEX extracts:
Rostering and scheduling:
- leave during in progress shifts and sessions,
- estimated travel warnings now available for all organisations, and
- roster period creation with a past start date.
The release also includes several bug fixes and other changes.
We’ve also included updates to permission sets.
Award Interpretation
Exclude travel time
Some organisations pay workers for travel distance (kilometres) but not for travel time (minutes). Previously, there was no way to separate these for payroll purposes — both were processed together when Timesheet Entries were created from an Appointment Travel record.
A new Exclude Travel Time From Timesheet setting in AWI custom settings controls whether travel time is included when Timesheet Entries are generated. It is disabled by default. Once enabled, workers are paid for kilometres travelled but travel time is not included in their Timesheet Entries. Travel start and end times continue to be recorded on the Appointment Travel record for reference. Reprocessing existing eligible worker appointments after enabling the setting will add or remove travel time accordingly. This has no impact on NDIS billing or claiming.
Reprocess leave after a worker assignment changes
System administrators can now mark an Availability leave record for reprocessing with a few clicks. We will be extending this functionality to other users such as Payroll officers in a future release. This is useful if a worker's Default Worker Assignment is updated after leave has already been processed to the payee timesheet, and removes the need to manually delete incorrect timesheet entries.
When the Mark for Reprocessing button is clicked on an Availability leave record, a pop-up displays all Leave Request Items (LRIs) linked to that leave, to select which dates need to be reprocessed. The next Process Leave batch or scheduled job will then delete and regenerate Timesheet Entries against the current Default Worker Assignment. Users can also trigger the batch immediately by ticking the Reprocess Leave Now checkbox. For more information see how to reprocess leave after a worker assignment changes.
Case Notes
Control case note visibility using sharing groups
A new Sharing Group field has been added to Case Note Templates, giving administrators a way to tag templates with a group name. When a case note is created from a template, the sharing group value is automatically stamped onto the note. Administrators can then configure Salesforce sharing rules using this field to restrict note visibility to specific user groups — for example, ensuring that notes created from a Support Coordination template are only visible to Support Coordinators.
The Sharing Group field is optional on templates, and has no effect on case notes created from templates where it is left blank. The field on the case note itself is populated automatically in the background from the template at the time the note is created.
Configuring sharing rules to make use of the Sharing Group field requires Salesforce administrator access.
If a Sharing Group value is added to an existing template, only case notes created from that point forward will have the value automatically stamped. For sharing rules to also apply to historical case notes created from that template, the Sharing Group field on those existing notes would need to be populated.
Lumary Engagement Console
This release includes updates that apply to organisations using the Lumary Engagement Console, powered by the Pendula for Salesforce Managed Package (version 3.0).
Console improvements
- Message status visibility — messages are now colour-coded to indicate outgoing queued (dark grey), sent (green), and error (red) states, making it easier to identify delivery issues at a glance.
-
Console refresh — the messaging window can now be refreshed manually or set to auto-refresh every 30 seconds, without reloading the full page.
- Activity Timeline — inbound and outbound SMS messages now appear chronologically in the Activity Timeline on any Salesforce record.
- Permission sets — the package now ships with native permission sets for controlling access to Console features, making it easier for Salesforce Administrators to manage user access without custom configuration.
| Permission set | Intended for |
|---|---|
| Pendula Console Viewer / Pendula4E - ReadOnly | End users who need to view message history |
| Pendula Console Composer / Pendula4E - Baseline |
End users who need to send and view messages |
| Pendula Administrator | Admins who manage Pendula settings |
| Pendula Template Designer | Admins who manage message templates |
| Pendula Integration User | The Pendula integration/service user (OAuth) |
Find more information on the related Lumary Engagement Console features.
Multi-recipient support
The Console now supports messaging multiple recipients from a single client record. A common scenario where a client has nominated all communications to be directed to the primary contact. Rather than storing the primary contact number on the participant’s record (creating duplicate data), users can now toggle to the client’s primary contact from the console and send messages directly to the appropriate person.
This reduces replicated contact data across your organisation and removes the risk of duplicate messages being sent to the same number.
SMS templates
You can now create and reuse SMS templates directly within Lumary. Templates are created by users with the Pendula Template Designer permission set and can be selected from the Console when composing a message.
This update means:
- Staff can send standardised messages without needing to build or manage Pendula flows, reducing dependency on trigger- or schedule-based automation.
- Users without prior Pendula knowledge can author and send templated communications entirely within Lumary.
Find more information on SMS Templates.
Observations tracking
Redesigned observations tracking on client records
The observation tracking functionality on client records has been rebuilt with a cleaner, more intuitive layout. Instead of displaying each individual observation schedule as a separate row, observations are now grouped by type — one card per observation type showing the type name, schedule summary, and the most recent observation recorded across all schedules of that type.
Filter pills at the top of the section let users quickly narrow observations by clinical category: Vitals, Output, Intake & Feeding, Neurological, Skin & Wound, and Other. Inactive schedules are hidden by default and can be revealed using the Show Inactive toggle.
Tapping a type card opens a detail view showing all individual schedules for that type, including start and end dates, time slots, the latest observation reading, and recent observation history. Observations can be added directly from the detail view, and schedules can be created, viewed or edited without leaving the client record.
These interface changes improve visibility and usability of tracking client observations for both desktop and mobile users.
Funding Period Enhancements
Edit individual period amounts independently
Providers can now manually edit individual funding period amounts on service agreements, to match a participant's actual plan structure including front loaded first periods and uneven initial allocations. Previously, allocations were automatically distributed based on the number of days in each period, which did not always align with the monthly splits used in a participant's NDIS plan. You can now override these calculated amounts to reflect the actual agreed funding for each period, ensuring service agreements accurately represent what has been negotiated and reducing discrepancies during billing.
Modify period start and end dates
Providers can now edit the start and end dates of individual funding periods directly from the view all periods modal on a service agreement aligning to a participant's actual plan structure. Previously, date adjustments required deleting and rebuilding the service agreement entirely. When a period's end date is changed, the following period's start date automatically adjusts to maintain continuity, and the same applies in reverse when a start date is modified. This makes it straightforward to accommodate NDIS plans that start mid-month, include plan reviews, or have unequal period lengths.
Prior Period Rollover transparency
The rollover amount carried forward from a prior funding period is now displayed as a standalone value in the funding period UI, giving providers clear visibility of how much of the available balance is new allocation versus rolled-over underspend from previous periods.
When a period closes with unspent funds, the balance automatically rolls over to the next period. The upcoming period card always reflects the current period's projected rollover in real time, calculated as: Allocation + Rollover − Delivered = Unspent Balance.
The rollover amount appears in two places:
- The "View All" funding periods modal, as a dedicated column after the Total column.
- The inline funding period component on the Service Agreement, shown on the active (highlighted) period, positioned below the Total row and above the Delivered and Committed rows.
Previously, the rollover amount was factored silently into the Remaining Balance, making it difficult to reconcile available funds or distinguish between plan-allocated totals and carry-forward amounts.
Enhanced funding period visibility
Inside each Support Category on a service agreement, the Funding Periods panel now shows a set of period cards designed to give you the most relevant information at a glance. Based on provider feedback, the panel displays exactly three periods:
The rollover amount appears in two places:
- One completed period: the most recently closed period, showing what was delivered and what rolled over.
- One current period: the active funding period with live balance figures.
- One upcoming period: the next period, with the projected rollover already reflected based on the current period's unspent balance.
Each period card shows the following six figures:
Field |
Purpose |
|---|---|
Allocation |
The dollar amount assigned to this period. |
Delivered |
The value of Service Deliveries (SDs) completed within the period. |
Unspent Balance |
Allocation + Rollover − Delivered. Funds not yet spent, regardless of what is scheduled. |
Committed |
The value of scheduled or rostered appointments falling within the period that have not yet been delivered. |
Forecast Remaining |
Unspent Balance − Committed. The projected end-of-period balance if all scheduled sessions are delivered. |
Rollover |
Unspent balance carried forward automatically from the prior period into this one. |
Travel & Transport budgeting and billing
Fixed travel & transport budgeting
Providers can now configure fixed travel and transport amounts directly on NDIS service agreements. When the Enable Fixed Travel and Transport Budgeting setting is turned on, an agreed fixed travel and/or transport value can be set per service agreement item, and is automatically applied to services delivered to claim the fixed amounts.
This includes total distance and time travelled to and from the appointment, total distance transporting the client, and whether a modified vehicle or bus was used. Users will still be able to record actual travel and transport values that will be stored separately when completing appointments.
NDIS July 2026 price guide changes
Service changes for 1 July 2026 pricing
Lumary has been updated to reflect the updated NDIS Pricing Schedule effective 1 July 2026. This includes new services added to the support catalogue, services with updated support item number suffixes, and services that have been removed. See our service changes for 1 July 2026 pricing for the full list.
The Pricing Arrangements and Price Limits (PAPL) has been rebranded as the ‘Pricing Schedule’.
Support Item Code Suffixes
ALREADY FIXED IN DC 2.17 Patch To align with the NDIA's July 2026 pricing update, we’ve updated the Service Delivered extraction process for applicable Allied Health services with a delivery date on or after 1 July 2026. When an applicable service has a claim type such as cancellation, non-face-to-face, provider travel, NDIA requested report (report writing), or telehealth, Lumary will append the suffix (_CA, _NF, _PT, _RR, or _TH) to the support item code automatically and append the Claim Type to the Service Name on the extract item when creating an extract.
These changes apply across the NDIS extract, financial extract, AR Management bulk invoice extract, and Invoice PDF. Additionally, Claim Type and Cancellation Reason will no be included in these extracts but will continue to be retained on the Service Delivered for your records.
For example, an SD with the support item 15_610_0128_1_3 - Assessment Recommendation Therapy or Training - Art Therapist with Claim Type of Non face-to-face, when extracted the item will use the support item code 15_610_0128_1_3_NF, and the name “Assessment Recommendation Therapy or Training - Art Therapist - Non Face-To-Face”
This change ensures compliance with the new NDIA reporting requirements while allowing users to continue to record SDs and claim types as they do today.
Updates for DEX extracts
DEX Stage 3 Changes
To support the Australian Department of Health's updated Data Exchange (DEX) requirements, we’ve introduced new mandatory fields for CHSP services, as per Data Exchange (DEX) Stage 3 Changes, effective from 11 August 2026.
The Stage 3 fields included are: Delivered By Third Party, Volunteer Direct Service, DEX Service Location Setting, Overnight Support Included, Engagement Time Minutes, Trip Distance (KM), Trip Time (mins), Meal Provided, Meals Cooked Offsite, Meals Texture Modified, Main Meal Count, Light Meal Count, Dessert Count, Beverage Count, and Snack Count. To view the new XML fields under the Session Node check out our DEX XML mapping to CM fields and objects article.
To enable this we have included the above fields on Service Delivered and Extract Items records, and have also introduced translations for DEX Service Location Setting. Validation has also been added to the DEX extract generation process to ensure the DEX Service Location Setting field is correctly populated before an extract is submitted.
For Providers required to report any of the new stage 3 fields, you will need to configure the DEX Service Type Specific Requirements in Lumary according to the requirements in your organisational data provided by DEX.
Service Delivery Entry (SDE) includes new DEX Stage 3 fields
To support the Australian Department of Health's DEX Stage 3 reporting requirements as per Data Exchange (DEX) Stage 3 Changes, the Service Delivery Entry (SDE) screen now dynamically displays the relevant DEX fields based on the DEX Service Type Specific Requirements selected. Users only see the fields relevant to the service being delivered.
The new fields cover a range of service-specific information, including whether a session was delivered by a subcontractor or involved a volunteer, overnight support, session location setting, engagement time, and time.
Further capturing meal details, trip distance and travel time, and assistance items.
Rostering and Scheduling
Leave during in progress shifts and sessions
When a worker's ad-hoc leave is raised mid-shift or mid-session, coordinators previously had no automated way to handle the scenario. Leave processing did not recognise in-progress appointments, leaving teams to manually adjust and complete them, and create vacancies for the remaining time.
This release introduces handling of leave raised mid-shift and mid-session. When a new leave request overlaps with a shift or a session a worker is currently in progress on:
- The leave creation screen now shows in-progress appointments alongside completed ones, so coordinators can see the full picture before confirming.
- Leave estimation now includes in progress worker appointments, from the leave start time to the scheduled end of the worker appointment. So this time is accounted for total leave hours.
- When leave is approved, the in-progress appointment is completed on behalf of the worker with the actual end date being when the leave started.
- Two new worker appointments are created for the remaining appointment time — one cancelled on behalf of the worker (to account for leave pay), and one unassigned so another worker can be allocated to cover the remaining time.
- Shifts, sessions, and worker appointments created through this process are linked together so they can be viewed and managed as a cohesive block.
Estimated travel warnings now available for all organisations
Estimated travel warnings launched as a pilot feature in the 2.16 release. From this release they are available to all organisations and turned on by default. Schedulers will now be able to view estimated travel warnings if triggered when creating new sessions, modifying session times or modifying a worker on a live calendar, roster period or base roster. Estimated travel warnings do not prevent a scheduler from proceeding; they are designed to surface potential travel conflicts caused by insufficient travel time between appointments. This reduces the chance of workers being unable to travel between appointments on time. The travel time and distance are estimated via the Google Routes API and are calculated based on:
- traffic conditions forecasted at the point in time of scheduling,
- the fastest route based on time,
- toll routes,
- and appointments within an 8-hour time frame (before and after).
The time and distance are calculated using the geo-location of the appointment. If an appointment does not contain a geolocation, it will default to the address, and if neither can be provided, it will be unable to calculate.
Roster period creation with a past start date
Schedulers can now create a roster period with a start date in the past. This supports go-lives that don't line up neatly with a roster cycle, where the go-live falls partway through a roster frequency and the current period has already started. Previously the start date had to be today or later, which forced manual workarounds in these mid-cycle go-live scenarios. Only sessions from today onwards are generated upon roster period creation. No sessions are created for past dates.
If a published roster period already covers the same date range, a duplication warning is shown and the user must click Save a second time to proceed. Existing draft and validated roster periods will continue to block creation of a duplicate roster period.
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, the Related Activity Type field is now pre-populated with a sensible default based on the context in which the note is being created. This helps prevent an issue where submitting a dictated case note without manually selecting a value would trigger a validation error and lose the dictated content.
The default values are: Appointment for standard client case notes (unless the template has the Assessment option enabled, in which case Assessment remains the default), House Shift for shift notes, and Other for house notes. Users can still change the Related Activity Type value if needed before submitting.
Client mobile files improvement - Support workers can now view case note files for a client directly within the client’s Files section of Lumary Mobile. Case note files are displayed for non-draft, non-private case notes.
Support Plan indicator improvement - Support workers using Lumary Mobile can now see at a glance whether a client has an active support plan when viewing the Site Clients list on a shift. A support plan indicator is displayed alongside each client's name where an active support plan exists. Tapping the indicator navigates directly to the client's record, where the support plan is displayed.
Support plans behavioural episodes improvement - When viewing a client's support plan that includes behaviours of concern on the Lumary mobile app, the card now shows pill indicators for any behavioural episodes captured today for that behaviour of concern. Each pill displays the episode type — ABC (if antecedent, behaviour, consequence details were recorded) or Gen (for general episodes) — along with the measure of severity. Tapping a pill reveals the episode duration.
Support workers can still tap the existing + Behavioural Episode button to record a new behavioural episode. Once saved, the new episode will appear immediately as an additional pill on the card without needing to reload the page.
Core
DEX Statistical Linkage Key (SLK) generation fix - We resolved an issue with the generation of the Statistical Linkage Key (SLK). Previously, when a client's first or last name was less than two characters long, the missing character positions in the SLK were incorrectly populated with '2'. These positions are now correctly filled with '9' to indicate that the name information is unknown, in line with the DEX SLK algorithm requirements.
New Task button fix - Resolved an issue where the New Task activity button was missing for certain user profiles on Contact (client, worker) and Enquiry records. The button appeared for some profiles but not others depending on how Salesforce resolved the underlying quick action, but is now available consistently.
Service Delivery Entry (SDE) fixes:
- We've resolved an issue on the Service Delivery Entry screen where clicking the edit (pencil) icon on a Service Delivered record would fail to open the edit modal. This occurred when a field such as Client Contribution was included the SD field set, causing the record to be uneditable. The edit modal now opens correctly regardless of custom field configuration.
- A fix has been applied to the Service Delivery Entry screen where apostrophes and double quotes in participant names, comments, and case notes were being incorrectly displayed as HTML character codes (such as
'and") instead of the actual character. Participant names, comments, and case notes will now correctly display these characters as literal text throughout the Service Delivery Entry screen.
AR Management
NDIA Payment reconciliation improvement - We have enhanced the invoice generation process for NDIS claims to resolve timing issues between claim submission and payment. Where NDIA has already processed payment before invoice generation runs (A claim is already marked as paid before an invoice has been generated), Lumary will now automatically create the invoice and the corresponding payment record simultaneously. This ensures that invoices are immediately transitioned to a 'Paid' status and correctly reconciled, removing the need for manual workarounds and preventing orphaned records.
ALREADY FIXED IN DC 2.17 Patch NDIS Remittance File fix - We've resolved an issue where processing a large NDIS remittance file would fail with a SOQL query row limit error, preventing payment records from being created and leaving the NDIS extract stuck in an unreconciled state. Payment records are now created successfully for remittance files of any size within supported platform limits, allowing the extract to reconcile and the billing workflow to continue without interruption.
Award Interpretation
Leave processing fix - We have enhanced the leave processing batch for improved stability and data integrity. The system now validates that all leave request items have both a start and end date/time before processing; if these fields are missing, the system will automatically flag the record, skip the leave processing for that item, and generate an integration log for review.
Roster Period estimation fix - We improved error handling of the Estimate Award Interpretation process so if the estimation fails to complete due to a time-out or other issue, clean-up steps are still executed ensuring no temporary records remain after the process exits.
User Management Console improvements:
Mobile phone numbers can now be entered in the console with spaces or hyphens, making it easier to see at a glance that the number has been entered correctly.
Administrators can set additional pre-fill values for Hourly Assignment fields within the User Management Console, including Assignment Rate Pay Code, Pay Rate Frequency, Auto Pay, Override Amount per Period, and Pro Rata Method. These defaults further reduce manual data entry when onboarding new workers.
Administrators can customise the list of timezones, profiles and permission set groups available when adding or editing Users through the console.
To preview the User Management Console see our article Get started with the new User Management Console
Worker Appointment processing fix - We have improved error handling for when a worker forgets to clock-out of a shift until the next day and then records travel or transport. Previously if the actual date and time for the worker travel record were in a different timesheet period than the session it applied to, this would either crash the job or create records in the subsequent timesheet period. Now any timesheet entries or items for travel will be created for the same date and in the same timesheet period as the related worked time.
Workforce management
Base roster fixes and improvements:
- Workers who had no base roster sessions were still appearing on the base roster calendar if they had sessions on a related roster period. We've resolved this so a worker only appears on the base roster calendar when they have base roster sessions or an active or pending contact availability template for that roster.
- After using the Roster from Template action to add sessions to a base roster, newly added sessions are now appearing on the calendar automatically without a hard browser refresh.
- When creating a group session in a base roster, expired group members are no longer being automatically pre-populated in the Client field. Schedulers can still manually add an expired member to the base roster session if needed.
- When draft roster functionality is enabled, removing a contact availability template (CAT) from a draft base roster fails for all users, including administrators. We have resolved this so CATs can be removed from draft rosters as expected.
Contracted hours fixes and improvements:
- When using the worker matching rule engine, the contracted hours shown under the employment type section were displaying incorrect values in the results. We have resolved this, so the correct contracted hours are displayed.
- The contracted hours check during roster period validation was incorrectly flagging violations for casual workers who had no contracted hours set — either null or 0.00. As casuals do not have fixed contracted hours, these flags were misleading for the rostering and scheduling team. The check now skips this rule for casual workers when their contracted hours fields are blank or set to zero.
Mobile fixes:
- When a worker started a session on Lumary Mobile and that session was subsequently cancelled, the Start Multiple Sessions check was incorrectly treating the cancelled session as still in progress. This blocked or warned workers from starting their next session. We have resolved this so cancelled sessions are excluded from the in-progress check.
- When support workers attempted to open Next up.. shift details, the shift page was loading incorrectly and displaying the session page layout instead of the shift layout. Navigating via My Upcoming Sessions was displaying correctly. We've resolved this so the shift page displays correctly regardless of how it is accessed.
- When a worker navigated to a shift located at a non-accommodation site, the app was displaying all clients associated with that site. This was intended behaviour for accommodation sites, but was a potential privacy concern for clinics and other non-accommodation locations. The client list on shift pages is now scoped to accommodation sites only.
Roster period fixes:
- When validating a roster period where a worker assigned to a session had no contact availability template linked to the roster, the availability rule was throwing errors instead of completing the validation cleanly. This only occurred when the Enable Rule Engine Log custom setting was enabled. We have resolved this so validation completes without error in this scenario.
- We've fixed an issue with the size of the Award Flags bell button displayed on the roster period.
- When a roster period was deleted, the nightly cleanup job was silently failing to delete some associated sessions. Sessions with a status of In Progress, Complete, or Cancelled were being blocked by a validation rule, leaving orphaned records in the system. We have resolved this so all sessions linked to a deleted roster period are cleaned up correctly regardless of their status. A cleanup script has been prepared for any orphaned records that accumulated before this fix.
- Published and expired roster periods were allowing actions that should not be available once a roster is finalised, including the ability to roster additional sessions, validate, publish, and delete the roster period. We have resolved this by hiding these actions on published and expired roster periods.
Rostering and scheduling fixes and improvements:
- When entering a planned service quantity above 99 in the session wizard or the Modify Clients & Services right-click action, users received a The number is too high validation error. The cap has been raised from 99 to 999 to support use cases where quantity represents kilometres or other high-value units.
- A new validation has been introduced when creating planned services via the session wizard, the Modify Clients & Services right-click action, and session completion. If a planned service references a support item with an expired or otherwise invalid rate, a warning is now surfaced to help coordinators identify potential billing issues before sessions are completed.
- We have resolved an issue when initiating a service agreement rollover with the Transfer base roster appointments checked, the transfer appointments screen would hang indefinitely if the client had a published roster period overlapping the rollover window.
- When assigning a worker via the Modify Workers right-click action, the system was incorrectly blocking the assignment if a different, cancelled worker on the same session had a shift that fell outside the session's time boundary. We have resolved this so related cancelled shifts are excluded from the boundary check.
- We have resolved an issue where workers with consecutive availability template entries running from 12:00am to 11:59pm were incorrectly flagged as unavailable for overnight and sleepover sessions and shifts. These workers are now correctly recognised as available.
Permissions
Permission sets
We’ve made updates to permissions on the permission sets shown in the following tables. 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 AR - AR Management |
Case Note |
Sharing Group |
Read, Edit |
| Extract Item | Beverage Count | Read, Edit | |
| DEX Service Location Setting | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Engagement Time (mins) | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Trip Distance (KM) | Read, Edit | ||
| Trip Time (mins) | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit | |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read, Edit | |
| DEX Engagement Time (mins) | Read, Edit | ||
| DEX Service Location Setting | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
| Lumary DC - Case Note Management | Case Note |
Sharing Group |
Read, Edit |
| Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit | |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read, Edit | |
| DEX Engagement Time (mins) | Read, Edit | ||
| DEX Service Location Setting | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
Session |
Session Summary |
Read |
|
Lumary DC - Goal Management |
Case Note |
Sharing Group |
Read, Edit |
| Lumary DC - Mobile Baseline | Case Note |
Sharing Group |
Read, Edit |
| Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit | |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read, Edit | |
| DEX Engagement Time (mins) | Read, Edit | ||
| DEX Service Location Setting | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
Lumary DC - Plan Assessment Upload |
Support Plan |
Record Summary |
Read |
| Lumary DC - Service Agreement Management | Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read | |
| DEX Engagement Time (mins) | Read | ||
| DEX Service Location Setting | Read | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read | ||
| Dessert Count | Read | ||
| Light Meal Count | Read | ||
| Main Meal Count | Read | ||
| Meal Provided | Read | ||
| Meals Cooked Offsite | Read | ||
| Meals Texture Modified | Read | ||
| Overnight Support Included | Read | ||
| Snack Count | Read | ||
| Volunteer Direct Service | Read | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
| Lumary DC - Service Delivery Management | Case Note |
Sharing Group |
Read, Edit |
| Service Delivered | Beverage Count | Read, Edit | |
| DEX Engagement Time (mins) | Read, Edit | ||
| DEX Service Location Setting | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Lumary DC - Session Management | Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read, Edit | |
| DEX Engagement Time (mins) | Read, Edit | ||
| DEX Service Location Setting | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
| Lumary DC - Set Up | Case Note Template |
Sharing Group |
Read, Edit |
| Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit | |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read | |
| DEX Engagement Time (mins) | Read | ||
| DEX Service Location Setting | Read | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read | ||
| Dessert Count | Read | ||
| Light Meal Count | Read | ||
| Main Meal Count | Read | ||
| Meal Provided | Read | ||
| Meals Cooked Offsite | Read | ||
| Meals Texture Modified | Read | ||
| Overnight Support Included | Read | ||
| Snack Count | Read | ||
| Volunteer Direct Service | Read | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
Lumary DC - Shift Note Entry |
Case Note |
Sharing Group |
Read, Edit |
Lumary DC - Template Management |
Case Note Template |
Sharing Group |
Read, Edit |
| Lumary - Mobile User | Service Agreement Item | Fixed Distance Transporting Client (KM) | Read, Edit |
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Modified Vehicle or Bus will be Used | Read, Edit | ||
| Service Delivered | Beverage Count | Read, Edit | |
| DEX Engagement Time (mins) | Read, Edit | ||
| DEX Service Location Setting | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | Read, Edit | ||
| Delivered By Third Party | Read, Edit | ||
| Dessert Count | Read, Edit | ||
| Light Meal Count | Read, Edit | ||
| Main Meal Count | Read, Edit | ||
| Meal Provided | Read, Edit | ||
| Meals Cooked Offsite | Read, Edit | ||
| Meals Texture Modified | Read, Edit | ||
| Overnight Support Included | Read, Edit | ||
| Snack Count | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Fixed Distance Transporting Client (KM) | Read, Edit | ||
| Fixed Distance Travelled From Appt (KM) | Read, Edit | ||
| Fixed Distance Travelled To Appt (KM) | Read, Edit | ||
| Fixed Transport: Modified Vehicle/Bus | Read, Edit | ||
| Fixed Travel / Transport | Read, Edit | ||
| Fixed Travel Time From Appt (mins) | Read, Edit | ||
| Fixed Travel Time To Appt (mins) | Read, Edit | ||
| Travel / Transport billing | Read, Edit | ||
Support Plan |
Record Summary |
Read |
| Permission set | Apex Class |
|---|---|
Lumary DC - Case Note Management |
enrtcr.BehaviouralEpisodeController |
Lumary DC - Lumary Baseline |
enrtcr.BehaviouralEpisodeController enrtcr__UMCDefaultsController enrtcr__UMCFieldDefaultsSelector |
WFM Permission sets
We’ve made updates to permissions on the permission sets shown in the following tables. 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 - Award Interpretation | Availability | Reprocess Leave | Read, Edit |
| Contact | Read, Edit | ||
| Gender [tc9_eau__Gender__c] | Read, Edit |
| Permission set | Apex Class |
|---|---|
| Lumary - Award Interpretation |
lmry__AWIUMCFieldDefaultsSelector lmry__AWIUserManagementConsoleController enrtcr__UMCDefaultsController enrtcr__UMCFieldDefaultsSelector |
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.
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.
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.