This article lists fixes that have been included in minor releases following the Lumary 26 release. It's a live status page, so please keep checking back for updates. You might need to refresh your browser to see the latest version.
Please note that not all issues affect all environments. Some issues may be specific to individual implementations.
Follow this section to get a notification when we add new release notes.
This article includes release notes for:
Lumary 26 minor release 1
We'll publish confirmation of what's been included by updating this page when the release is made available in production environments.
Available from: 24 November 2026
Version: [TBC]
We've added improvements for financial extracts, rostering and scheduling, security, custom extracts, service agreements, Service Delivery Entry, and DEX reporting.
Financial Extract improvements:
NDIS July 2026 price guide changes:
Rostering and scheduling:
- choose which service agreement item a planned service uses
- new DEX Stage 3 fields on sessions and planned services, and
- worker status and employment date validation.
Security:
Self serve Custom Extracts:
Service agreement improvements:
- configurable columns on NDIS service agreements
- hide expired service agreement items
- remaining amount on service agreement items
- inactive rate types hidden when creating service agreements, and
- Service Booking Number accepts whole numbers only.
Service Delivery Entry (SDE) improvements:
Updates for DEX reporting:
The release also includes several bug fixes and other changes.
We've also included updates to permission sets.
For customers using Lumary Sessions - We're also including Lumary CM Mobile updates as part of this release. See Lumary CM Mobile 1.7 release notes for more information.
Financial Extract improvements
Individual Grant Service Delivered records in the Financial Extract
Service delivered records linked to Individual Grant service agreements are now included in the financial extract. Providers can now extract this financial data alongside all other service delivered records, provided the standard extract conditions are met, including that the Rate Type has Financial Extract selected in the Include in Extracts field. Any eligible records that haven't been extracted yet will be included the next time you run a financial extract that covers their dates.
NDIS July 2026 price guide changes
Support Item Code Suffixes
ALREADY FIXED IN Lumary 26 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 longer be included in these extracts but will continue to be retained on the service delivered record 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.
Rostering and scheduling
Choose which service agreement item a planned service uses
When a client has more than one current service agreement item for the same service, you can now see and choose which one a planned service is booked against. Previously, the system picked one for you, and you couldn't see or change which one it used.
This helps when a client has:
- overlapping service agreements, such as an old agreement and its renewal running at the same time,
- more than one item for the same service on one service agreement, such as to set up different delivery patterns, or
- the same service under different plan management providers.
When you add a planned service to a session and save it, a service agreement item is still selected automatically. If more than one item matches, an orange icon appears on the planned service. Hover over it to see how many items match, then click Edit on the planned service to check or change the selection.
Each option shows:
- the service agreement item and its service agreement,
- the service agreement's start and end dates, and
- the remaining funds and remaining quantity. For unrestricted categories, it shows the remaining balance of the support category.
Only items that match the planned service's claim type are listed, so a non-face-to-face claim type only shows non-face-to-face items. The Funding Management field now only appears when there's more than one option to choose from.
For group sessions, the New Session wizard now shows planned services grouped by client, before the session is created. Previously, it showed a single planned service with all clients selected in one list. You can now see and check the planned service for each client on its own.
We've also improved how fields behave when you create or edit a planned service. Each field now stays read-only until the fields before it are filled in and its options have loaded, so fields no longer appear blank and ready to fill in before you can use them.
New DEX Stage 3 fields on sessions and planned services
To support DEX (Data Exchange) reporting requirements, new fields have been added to sessions and planned services, covering details such as service location setting, whether a service was delivered by a third party, and meal, engagement, and travel information for a session. These fields can be added to session and planned service screens using existing custom field sets, and any values entered will flow through to the resulting service delivered records.
Worker status and employment date validation
Validation rules are now available to prevent a worker's status change from leaving employment dates incomplete. Once enabled, a worker's status cannot be changed to Inactive unless an end date is populated, and cannot be set to Active unless a start date is populated. Workers can still be created as Inactive without an end date, which supports data loading. Existing records will not be affected when validation rules are enabled, and if enabled, the end date validation only fires when the status is changed on save. These validation rules will not apply if enabled for organisations using EasyEmployer as their rostering system.
To enable the Employee Active Start Date Required validation rule
- Log in to the org as a System Administrator.
- Navigate to Setup > Object Manager > Contact > Validation Rules.
- Click Employee_Active_Start_Date_Required.
- Click Edit.
- Check the Active checkbox.
- Click Save.
To enable the Employee End Date Mandatory validation rule
- Log in to the org as a System Administrator.
- Navigate to Setup > Object Manager > Contact > Validation Rules.
- Click Employee_End_Date_Mandatory.
- Click Edit.
- Check the Active checkbox.
- Click Save.
Security
Salesforce session timeout and mobile app lock
For organisations using Lumary sessions, we're updating the recommended Salesforce session timeout and mobile app lock settings to better protect client information, while keeping sessions practical for day-to-day work.
- Desktop logins will stay valid for 4 hours.
- Mobile app logins will stay valid for 24 hours, covering a full shift without timing out partway through.
- If the app isn't used for 10 minutes, it will lock - users get straight back in with their phone's PIN, fingerprint, or Face ID, rather than a full sign-in.
These settings are being applied to Lumary profiles as part of the November release, but customers who opted out following our recent communication, or those that use Skedulo, won't be changed. If your organisation uses custom profiles, reach out to Lumary support for the steps to apply the changes.
Self serve Custom Extracts
Improved completion confirmation
We've improved the Review and Complete stage of the custom extract creation process. The final step now displays a confirmation that the extract has been generated successfully, along with a summary of the extract's key details and guidance on what to do next. This gives users clearer visibility of what they've created and confidence that the process has completed.
Enhanced Formula Builder
Custom extracts now include a no-code Formula Builder for mapping extract item fields, making it easier for administrators to configure extracts without needing to understand technical concepts such as modes, JSON structure or field API names. You can now choose between 2 mapping approaches:
-
Basic - map the source field directly to the target field with no calculation.
-
Advanced - open the Formula Builder to construct a calculated value using standard formula syntax. Click Validate to check the formula. A confirmation or a plain-language error message appears beside the button.
This allows more complex extract columns to be configured directly in the interface, without needing to write technical expressions or involve a developer.
Find out how to create and configure a custom extract.
Group By configuration
Custom extracts now include a Group By configuration interface, allowing administrators to group the output of a custom extract so related records are kept together, labelled with a generated identifier, and presented in the layout your file needs.
By default every row in a custom extract output file is a standalone record, and the file has no sense of which records belong together. Grouping changes that. You choose up to three fields to group by, and records that share the same values across those fields form a group. Lumary orders the file so each group's records sit together, and adds a generated identifier column that labels each group.
Two separate settings control how the file looks. The display mode controls how the identifier column behaves. Compact Grouping controls how the group-by field columns behave. The two are independent, so any display mode can be combined with Compact Grouping switched on or off.
Find out how to group the output of a custom extract.
Service agreement improvements
Configurable columns on NDIS Service Agreements
Administrators can now customise which columns show for service agreement items (SAIs) on NDIS service agreements, and the order they appear in. Choose up to 13 columns to display alongside the SAI Name, using the new NDIS SAI Columns setting in the Lumary Settings > Service Agreements tab. Existing organisations keep their current columns until an administrator changes them.
On the Service Agreement page, the Name column and the column headings now stay in place as users scroll, and the item list scrolls sideways when there are more columns than fit on screen.
This configuration applies to NDIS service agreements only. Find out more about how to configure columns for NDIS agreements.
Hide expired service agreement items
Service agreement items whose end date has passed are now hidden by default on the Service Agreement Items list. When an agreement has expired items within it, a toggle labelled with the number of expired items (for example, Show 1 expired item) lets you show them across every category at once. Expired items are highlighted in red when shown, so they're easy to tell apart from active items. The expired toggle and highlighting isn't shown on Home Care Package (HCP) or Support at Home (SAH) agreements, on agreements with Expired status, or when an agreement has no expired items.
Find out more about how to show expired service agreement items.
Remaining Amount on service agreement items
We've added a Remaining Amount column to the Service Agreement Items list, showing the remaining dollar value for each line item at a glance. This is available on service agreements with NDIS, Block Grant, and Individual funding types.
Inactive rate types hidden when creating service agreements
When creating a service agreement, inactive rate types no longer appear in the Funding Type and Rate Type picklists for NDIS, Individual Grant, and Block Grant agreements, reducing the risk of agreements being set up against outdated or invalid rates. The Other funding type is always displayed. The Active field now appears on rate type (reference data) records, so you can see at a glance whether a rate type is available to use. To keep data consistent, a rate type can no longer be marked inactive while it still has active rates. As part of this release, any inactive rate type that has at least one current rate on the day the release is applied will be automatically set to active, so those rate types stay available when creating service agreements.
If your organisation uses a customised Rate Type page layout, the field won't be added to it automatically. A system administrator will need to add Active to the customised layout. For instructions, see Identify a customised page layout and add a field.
Service Booking Number accepts whole numbers only
The Service Booking Number field now only accepts whole numbers. Decimal places, letters, and special characters are blocked when creating or editing service bookings. This prevents invalid booking numbers being entered and keeps them aligned with the whole numbers used in PRODA/myPlace.
Service Delivery Entry (SDE) improvements
Faster loading on high-volume days
The Service Delivery Entry screen has been improved to load records more efficiently on days with a high volume of service delivered entries. Records load in batches; to see more, scroll to the list's end and click the new Load More button. If you're working with more than 2,001 records in a single day, you'll need to add additional filter criteria (e.g. client or worker) to access records beyond this threshold. This keeps the page responsive even on your busiest days, so you can keep working without delays.
Updates for DEX reporting
Capture DEX Stage 3 information on Skedulo jobs
This release requires Lumary Services for Skedulo v1.387 and Skedulo AU Healthcare v9.15 or later. If you're using Skedulo, make sure these versions are installed before you capture DEX information on Skedulo jobs.
Providers using the Skedulo integration can now capture DEX Stage 3 reporting information on Skedulo jobs and have it carried through to the service delivered records created when a job is completed. This works for both single and group bookings, so you no longer need to enter this information again in Lumary before DEX reporting.
Schedulers and support workers can record the following on the job:
- Delivered By Third Party
- Volunteer Direct Service
- DEX Service Location Setting
They can record the following on each job service item:
- Overnight Support Included
- Meal Provided, Meals Cooked Offsite, and Meals Texture Modified
- Main Meal Count, Light Meal Count, Dessert Count, Beverage Count, and Snack Count
- DEX Engagement Time Minutes, DEX Trip Time (mins), and DEX Trip Distance (KM)
These fields aren't currently available on job service items for services from an unrestricted category. We've raised this with Skedulo and will share an update once it's resolved.
The three job fields are turned off by default. If your organisation reports to DEX, an administrator needs to activate them in Custom Settings > Skedulo Additional Fields. Once they're active, the fields display in the Additional Fields section of the job.
The job service item fields display automatically when a service's DEX service-specific requirements are set up correctly. Check these requirements for each service type your organisation delivers.
DEX Extract improvements
The Prevent Delivered Record Modification setting in Lumary Settings now also applies to service delivered records that have been extracted into a DEX extract. Previously, DEX-extracted records could still be edited or deleted after being reported to DEX. When the setting is enabled, attempting to edit or delete a DEX-extracted service delivered record will now be blocked with the standard message advising that service delivered records cannot be changed once extracted. This ensures your delivered service data stays aligned with what has been reported to DEX.
Validation has also been added to ensure that when the DEX Activity Specific Requirements include ACCOMMODATIONTYPE or HOUSEHOLDMANDATORY, the corresponding field must be set on the client: Accommodation Setting for ACCOMMODATIONTYPE, and Household Composition for HOUSEHOLDMANDATORY. If either field is missing, users will receive a clear error message against the client record during the extract process, ensuring client details are complete before the file is submitted to DEX.
Bug fixes and other changes
The following bug fixes and changes are also included in this release.
Auto-generate Service Delivered Records fix - We resolved an issue for auto-generate service delivered records where the Delivery Scheduled Date on a service agreement item did not recalculate when the funding schedule was edited. Previously the date updated only in two cases: when it had not been set, or when the funding schedule's start date was in the future. If the start date had passed, changing the start date or the delivery days did not affect the Delivery Scheduled Date, and automatically generated service deliveries continued to follow the original schedule.
Now, when the funding schedule's start date is in the past and the item has no service delivered records, the Delivery Scheduled Date recalculates from the funding schedule and can move earlier if the new schedule requires it. If service delivered records already exist, the date may move later but will never move earlier, so already generated deliveries remain unaffected.
Beds history tracking - Changes to bed names will now show in the history related list on bed records.
Recommended practice: renaming of beds should only be used to correct a genuine data entry error (e.g. a typo at setup). For any other change, such as room repurposing or a site restructure, decommission the existing bed (make it inactive) and create a new one, to preserve historical reporting accuracy.
Beds Calendar fix - We've resolved an issue where bed allocations for services with an hours unit of measure dropped any part of an hour when service delivered records were generated. For example, a bed allocation from 12:00 AM to 10:45 PM (22 hours and 45 minutes) was charged as 22 hours instead of 22.75. Service delivered records now charge the full time, including partial hours, for both pre-charge and post-charge billing and on the first and last days of multi-day bookings.
Block grant contact status fix - On Block Grant service agreements, contact status for a client no longer changes automatically when a service delivered record is entered against a different funded client on the same grant service agreement. Previously, contacts with status Waiting were reset to Current whenever any activity occurred on the service agreement, even if the contact was not involved. Contact status now updates only for contacts to which the service delivery directly relates, so manually set statuses are retained.
DEX Extract fixes:
- We've resolved an issue where the DEX extract XML created duplicate session-level elements for group sessions. Where a group session includes multiple service delivered records, elements such as IsSubcontractorDelivered are now written once per session, using the values from the first service delivered record. Where these values differ between service delivered records in the group, each record is written as a separate session in the XML. Trip Time and Trip Distance are also now mapped to the correct fields in the XML.
- We fixed an issue where, if Meal Provided was No/false in the XML, the DEX extract for CHSP reporting still included conditional meal fields (Is Items Texture Modified, Main Meal Count, Light Meal Count, Dessert Count, Beverage Count and Snack Count), causing DEX rejections. These fields are now omitted from the XML when Meal Provided is No, and included only when Meal Provided is Yes or when the service type requires meal counts without Meal Provided (for example, Meal Delivery). When a service's DEX requirements include Meal Provided and Meal Provided is set to No on a service delivered record, the DEX extract now flags any meal counts recorded against that record before the extract is generated, so discrepancies can be corrected before submission.
Funding periods fix - We've resolved an issue where changing the Funding Period Length on a service agreement category could create duplicate or overlapping funding periods if any of the category's periods had been manually adjusted. When you change the Funding Period Length now, all existing funding periods for that category, including adjusted ones, are replaced with new periods at the new length. The new periods cover the service agreement's full start-to-end date range. This keeps committed, delivered, and unspent totals accurate.
Before the existing periods are removed, a warning asks you to confirm the change. Click Proceed Anyway to continue, or Back to keep the current periods. Any adjustments made in Adjust Periods will need to be made again after the new periods are created.
Incident Management settings fix - We've resolved an issue where an incident could use the notification recipients and owner from an Incident Type Override for a different Sub Type. When an incident's Type only had overrides for other Sub Types, the incident used one of those overrides instead of the Default settings. Incidents now use the override that matches their Type and Sub Type, then a Type-only override (with no Sub Type) if there is one, and otherwise the Default settings. This applies to incidents submitted after the upgrade.
Incident owner reassignment fix - We've resolved an issue for organisations with the Incident Ownership and Notification feature enabled and Private sharing settings with sharing rules on the Incident Management object, where reassignment rules move ownership away from the submitter. In this scenario, if the person submitting the incident wasn't part of the access group, the owner change would fail to save, with no error shown to the user, even though the incident itself was created successfully.
Incident owner reassignment now completes correctly regardless of the submitter's access level. When the incident is reassigned to someone other than the submitter, the submitter now sees an "Incident submitted successfully!" confirmation. If the incident owner remains the submitter, they're taken to the new incident record as before.
Lumary Settings fix - We've corrected the help text on the Modified Vehicle Transport Rate and Non-Modified Vehicle Transport Rate fields in Lumary Settings, under the Travel and Transport tab. The help text previously referred to the rate being defined in minutes, when these rates apply to transport kilometres. The wording now correctly refers to kilometres, so the default organisation transport rates are clearer to configure.
NDIS Extract fix - We've resolved an issue where the SupportsDeliveredFrom date on NDIS claims could fall outside the service agreement date range for weekly line items. Previously this date was calculated as the service delivered date minus six days, which could land before the service agreement start date and result in the claim being rejected. Where the calculated date is earlier than the service agreement start date, the extract now uses the service agreement start date instead. The claim period is now also stored against the extract item in the new Supports Delivered From and Supports Delivered To fields, which are used when the .csv claim file is generated.
PMHC MDS Extract fix - The PMHC MDS Episode Extract now sets the organisation type at episode conclusion only when the episode has actually concluded. Episode Completion Status is no longer defaulted to 0 and remains blank when no value is recorded, aligning with the PMHC data specification, which does not require Episode Completion Status. This ensures episodes.csv reports conclusion data only for episodes that have genuinely concluded.
Recurring sessions fix - We've fixed an issue where recurring sessions could be rostered outside the date range of a planned service's service agreement item (SAI). In the New Session Wizard on the Sessions Calendar and on the Session record page, a recurrence now can't be saved if its first session starts before the SAI start date, or its last session starts after the SAI end date. When a recurrence pattern falls outside these valid dates, users will receive a clear error message identifying the affected client, SAI, and the specific date range required. In the New Session Wizard, Save and Save and Roster stay disabled until you change the recurrence pattern to fit within the valid agreement period. This doesn't change any recurring sessions that are already rostered outside the SAI date range.
Service Agreement Rollover fixes:
- When a service agreement is rolled over, category Start and End Dates now update to align with the new agreement's dates rather than carrying over the original dates. This keeps category dates consistent with the rolled-over agreement period and prevents related issues with service agreement items.
- We've resolved an issue where the Allocated to Services and Unallocated values on a service agreement created through rollover were incorrect. The Allocated to Services value was carried across from the original service agreement rather than reflecting the new one, meaning the totals didn't reconcile. These values are now calculated from the support categories and line items on the new service agreement.
Service Delivered fix - Deleting a service delivered (SD) record now also deletes its related apportionment, appointment travel and non-labour cost records, so they're no longer left orphaned. This also covers any child travel and transport SD records deleted with the parent. SD records linked to a planned service, such as those created by completing a session, keep their related records. Any appointment travel linked to a worker appointment is also kept, so worker travel is still there for timesheets and worker costs.
Service Delivery Entry (SDE) fix - We've fixed an issue on the Service Delivery Entry screen where the Charge Centre Capital Cost checkbox would disappear when switching to another service that also allows Centre Capital Cost. When switching between two services that both allow Centre Capital Cost, the checkbox now correctly remains visible, giving users the ability to uncheck it if they don't wish to charge these costs.
Sessions fix - We've resolved an issue where deleting a session failed with an error when the session, or one of its related records, was owned by a different user. This affected schedulers deleting a session created by another scheduler. Sessions and their related records can now be deleted by schedulers regardless of who owns them.
Site Service/Program fix - We've fixed a bug where planned services related to an unrestricted support category were saved without a Site Service/Program. This caused services delivered to be created with an empty Site Service/Program as well, which left DEX reporting incomplete. The Site Service/Program is now filled in automatically from the matching site, service and program, on both planned service and the service delivered records.
Smart file uploader fix - When creating a new Personal Support Plan via the smart file uploader, the Plan Type field is now presented during record creation (previously only Record Type, Plan Date, and Status were prompted).
AR Management
Allocate Unallocated Payments improvement - We've improved the stability of the Allocate Unallocated Payments screen in AR Management. The screen has been rebuilt to ensure it loads and functions reliably across all organisations, eliminating errors that previously prevented users from completing payment allocations. No changes have been made to how you allocate payments.
NDIS Payments improvement - Payments created from NDIS claim results can now use the date NDIS paid the claim. This means receivables in the finance journal extract match the NDIS remittance for any reporting period.
We've introduced a Payment Date field on NDIS extract items to record the date NDIS paid the claim, which is used when the item's payment is created. If the Payment Date is blank when the item is marked as paid, it's set to today's date. When you upload an NDIS remittance file, the Payment Date is set to the processing date, because the remittance file doesn't include the date NDIS paid the claim.
If the Payment Date falls in a closed accounting period, or in no accounting period, the payment is still created and posted but will carry a blank accounting period, which may require manual assignment.
If you use Lumary's NDIA Integration Module, the Payment Date will be filled from the NDIA remittance once version 1.17 of the module is installed. Until then, payments keep using the date the results were processed.
Permission Set fixes - We've resolved an issue where users were unable to allocate payments against an invoice. Access has now been granted through the Lumary AR - AR Management permission set, so all users with AR Management permissions can allocate payments as expected.
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 - Advanced | Extract Item | Payment Date | Read, Edit |
| Reference Data | Active | Read, Edit | |
| Lumary - Aged Care | Planned Service | Beverage Count | Read, Edit |
| DEX Engagement Time Minutes | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | 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 | ||
| Session | DEX Service Location Setting | Read, Edit | |
| Delivered By Third Party | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Lumary - Basic | Reference Data | Active | Read |
| Lumary - Extracts | Extract Item | Payment Date | Read, Edit |
| Supports Delivered From | Read, Edit | ||
| Supports Delivered To | Read, Edit | ||
| Lumary - Mobile User | Planned Service | Beverage Count | Read |
| DEX Engagement Time Minutes | Read | ||
| DEX Trip Distance (KM) | Read | ||
| DEX Trip Time (mins) | 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 | ||
| Session | DEX Service Location Setting | Read, Edit | |
| Delivered By Third Party | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Lumary - Rostering | Planned Service | Beverage Count | Read, Edit |
| DEX Engagement Time Minutes | Read, Edit | ||
| DEX Trip Distance (KM) | Read, Edit | ||
| DEX Trip Time (mins) | 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 | ||
| Session | DEX Service Location Setting | Read, Edit | |
| Delivered By Third Party | Read, Edit | ||
| Volunteer Direct Service | Read, Edit | ||
| Lumary - Standard | Reference Data | Active | Read |
| Lumary AR - AR Management | Extract Item | Payment Date | Read, Edit |
| Supports Delivered From | Read, Edit | ||
| Supports Delivered To | Read, Edit | ||
| Planned Service | Beverage Count | Read | |
| DEX Engagement Time Minutes | Read | ||
| DEX Trip Distance (KM) | Read | ||
| DEX Trip Time (mins) | 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 | ||
| Session | DEX Service Location Setting | Read | |
| Delivered By Third Party | Read | ||
| Volunteer Direct Service | Read |
Custom settings
The below custom setting access has been added to the relevant permission sets as part of this release.
| Permission set | Custom Setting |
|---|---|
| Lumary - Advanced | Lumary Extended Settings |
| Lumary - Basic | Lumary Extended Settings |
| Lumary - Standard | Lumary Extended Settings |
Apex Classes
The below Apex Classes have been assigned to the relevant permission sets as part of this release.
| Permission set | Apex Class |
|---|---|
| Lumary AR - AR Management | enrtcr.ARAllocatePaymentController |
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. When we change live articles, we republish them so that followers are notified of any updates!
To follow the section that contains this article:
- Go to the CM minor releases section. This section currently appears under Releases > CM releases.
- 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 and the label on the button will change to Following. The system will send you an unstyled version of new or updated pages.
You can cancel these notifications at any time by:
- using the link at the end of the email, or
- going to the CM minor releases section and clicking on Unfollow.