This article lists fixes that have been included in minor releases following the last major 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.
This is a live page, so please follow the section to get a notification when we update the page.
This article includes release notes for:
- Lumary 21 minor release 5
- Lumary 21 minor release 4
- Lumary 21 minor release 3
- Lumary 21 minor release 2, and
- Lumary 21 minor release 1.
Applied improvements |
Lumary 21 minor release 5 |
Available from: 26/8/2024 Version: 21.129 We've begun to deploy Lumary 21 minor release 5 to production environments. We've added improvements for: We've also included updates to permission sets. Other improvements and fixes are summarised in the following table. |
Feature/function | Improvement |
---|---|
Sessions | When completing sessions, overclaim checks now correctly consider negotiated rates. |
Skedulo |
When service delivered (SD) records are created from Skedulo jobs linked to a program, the program value is now being populated on the SD record. |
Incident Management We've made several changes to improve the recording of information in the Incident Management forms. These changes are aimed at improving efficiency by:
Users can now also capture whether a restrictive practice was used during an incident. Radio buttons The buttons we used previously were unable to retain selections. We've replaced them with radio buttons so that values are stored when the user navigates away from the current screen by clicking the Next or Previous buttons. This change has been made to questions that capture information like whether:
Multiple screens We've separated the questions into multiple screens. This is partly due to the extra space taken up by the vertical radio buttons. These changes have also improved the visibility of data validation alerts. Now that values can be retained for the radio button selections, users will immediately be able to see fields that have been missed or have errors. Rich text fields We've made improvements to the rich text fields. These include:
Feedback capture We've also fixed some issues that affected options when the user attempted to capture feedback. When a user added an invalid phone number, the previous form structure meant that it was unclear what error they had made. It also removed other information that they'd already added as the feedback record was not saved. With our improvements, the user is:
Information added to the What action you would like taken / preferred outcome? field is now stored on the feedback record. Find out how to record an incident using the updated features. NDIS short notice cancellation We've added new fields and functionality to apply the NDIA's revised short notice cancellation policies to cancelled NDIS services. These fields have been added to the Service object to capture:
As well as supporting the July 2024 pricing update, this change gives providers the option to set more lenient cancellation policies. Default values will be applied to these fields as per the NDIA's July 2024 pricing arrangements and price limits. The new fields require additional permissions. If you have custom or cloned permission sets that include the Service object, we recommend that you add these permissions. Cancellation Claim Notice Period The Cancellation Claim Notice Period field is a numerical field that captures the number of days within which cancellation can be claimed. It is:
Find out how to set a more lenient cancellation claim notice period. Cancellation Claim Days Policy The Cancellation Claim Days Policy field captures how to count days for short notice cancellations. It can be set to:
Public holidays Due to regional variations, the functionality does not currently support public holidays being excluded from clear business days. A solution for this is being planned for a future release. In the meantime, providers may need to use the Service Delivery Entry screen to create service delivered (SD) records for cancellations where the notice:
Service agreements To improve efficiency, we've made improvements to the way service agreements handle changes. Users no longer need to refresh the page:
We've also improved the handling of negotiated rates on service agreement line items. If the rate's GST Code does not incur GST, the Negotiated Rate GST Amount automatically populates as zero. This requires the GST code's GST percentage to be set to 0. Find out how to set the GST percentage on a GST code. 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 - Advanced | Service | Cancellation Claim Days Policy | Read |
Cancellation Claim Notice Period | Read | ||
Lumary - Basic | Service | Cancellation Claim Days Policy | Read |
Cancellation Claim Notice Period | Read | ||
Lumary - Standard | Service | Cancellation Claim Days Policy | Read |
Cancellation Claim Notice Period | Read | ||
Lumary - Incident Capture and Management | Incident Management | Observation Date | Read, Edit |
Was a restrictive practice used | Read, Edit |
Back to minor 5 links |
Lumary 21 minor release 4 |
Available from: 24/6/2024 Version: 21.100.2 We've deployed Lumary 21 minor release 4 to production environments. We've added improvements for: We've also included updates to permission sets. Other improvements and fixes are summarised in the following table. |
Feature/function | Improvement |
---|---|
Ad hoc services | A client no longer requires at least one service agreement to allow the delivery of ad hoc services through the Service Delivery Entry screen. |
Associated providers | We've relabelled the Clinic field on associated provider records to Organisation. This is to reflect that users can use this field to select agency/other or clinic accounts. |
Beds Calendar | We've made it easier to find the right client when adding or editing bed allocations and multiple clients have the same name. When searching the client field, it now shows their:
|
Case notes |
Users can now add a title to a case note from the Service Delivery Entry screen. When adding a service delivered (SD) or ad hoc service, users can add a title using the Case Note Title field. To create a case note record, they'll also need to fill in the Case Note field. If the Case Note field is populated and the Case Note Title field is left blank, the SD record number will be used to populate the title. |
Client photo |
The client photo upload limit now reflects the current Salesforce 3 MB limit. A warning will display if users try to upload larger files. The client photo field has been set to display this limit. Providers with customised client records may need to update their layouts to reflect this change. |
Funding management | We've added a filter for providers who have enabled funding management selection at the agreement item level. When a category or item uses a registered plan management provider, users need to select a funding manager. The Funding Manager field is now filtered to only show accounts that are Agency/Other. This:
|
NDIS travel and transport |
We've updated the warning messages to support changes made to travel and transport in Lumary 21. When completing a session for a service agreement where travel and transport rates have not been set:
The system was previously also checking the service agreement settings, which can now be blank due to changes released in Lumary 21. |
We've updated how the rate shows for the Total Distance Transporting Client (KM) field when adding or editing an SD record from the Service Delivery Entry screen. When ticking or unticking the Modified vehicle or bus was used checkbox, the rate shown now changes correctly. This is only a cosmetic change, as the system was already using the correct rate to calculate costs when creating SD records. | |
Rates | We've updated some validations to allow providers to change the end dates on non-NDIS rates. |
Service Delivery Entry | We've extended the optional search fields on the Service Delivery Entry screen. The Client, Service Agreement and Worker (User) fields are now wider. This makes it easier to search for and view longer entries in these fields. |
Sessions | We've fixed an issue that was preventing SD records from being generated when completing sessions scheduled on the first or last date of service agreement items. |
Skedulo for aged care providers | Users can now select unrestricted categories from HCP agreements in Skedulo jobs when the agreement has no end date. |
Service agreements We've made updates and fixes to improve the efficiency of setting up and managing service agreements. With these changes:
Block service agreements We've made several adjustments to block service agreements to remove unnecessary features. This includes:
For providers with block service agreements that have a large number of funded clients and SD records, we've improved SD creation and funded client updating. An hourly batch job now updates the Amount Delivered values on funded client records. Due to Salesforce limits, we recommend providers avoid creating more than 25,000 SD records for a single agreement. We recommend use of the rollover function to create a new agreement before reaching this limit. Claim types We've made it easier to identify claim types in the Service Delivery Entry screen. We've added the Claim Type column to the Services Delivered list. This shows the API name of the claim type, for example, NF2F for non face-to-face services. We've fixed issues so that the claim type for non face-to-face services is populated when:
We've also fixed an issue that occurred when editing the claim type on an SD record in the Service Delivery Entry screen. Where Apportion Primary Service is selected, the client portion value will now be retained. 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 - Advanced | Service Delivered | Case Note Title | Read, Edit |
Lumary - Basic | Service Delivered | Case Note Title | Read, Edit |
Lumary - Standard | Service Delivered | Case Note Title | Read, Edit |
Back to links |
Lumary 21 minor release 3 |
Available from: 22/4/2024 Version: 21.65.2 We've begun to deploy Lumary 21 minor release 3 to production environments. We've added improvements for:
We've also included updates to permission sets. Other issues we've fixed and improvements are summarised in the following table. |
Feature/function | Improvement |
---|---|
Service agreements | Rolling over an agreement that has service agreement items that end before the rollover date no longer incorrectly extends the end date on those items. |
Changing an agreement's dates no longer causes false validation errors when editing its service agreement items. | |
Service Delivery Entry screen | Scrolling over a numeric field when you add or edit a service delivered (SD) record from the Service Delivery Entry screen no longer affects the field's values. |
Sessions auto complete | We've fixed an issue that was preventing some ScheduledSessionsAutoComplete jobs from running successfully. |
Personal identifier records | Providers with more than 50,000 personal identifier records are no longer prevented from converting an enquiry to a client. |
Incident management | Creating a corrective action record now links that record to the related incident. This applies to users with the Lumary - Incident Capture and Management permission set. |
Alert handling | When their associated records are changed, alerts are now updated rather than being deleted and recreated. |
Skedulo |
We've improved the handling of group event jobs when an attendee is marked as a billable cancellation or not attended. The cancellation reason on the SD record will match the reason selected on the Skedulo job. We've also added Skedulo jobs to recent service agreement rollover improvements. Future scheduled jobs can now be moved to a new rollover agreement. |
NDIS provider travel and activity based transport This release improves the flexibility of non-labour costs for provider travel and activity based transport services. Providers will now be able to add these services to NDIS service agreements as separate service agreement items. This improvement means that these services can:
Find out how to add provider travel - non-labour costs and activity based transport as separate service agreement items. Check out the following video for an introduction to these new features. Support item codes In some categories, there are multiple versions of these services with the same name, for example, activity based transport. To help users identify the relevant service, we've added the support item codes to the end of service names in:
Child service delivered (SD) records When these services are added as separate service agreement items, child SD records will link to the separate items when generated from:
If they're not added as separate items, child SD records will link to the parent service agreement item listed on the service agreement, as per current functionality. If your organisation set up its own workaround for adding these services as separate items, child SD records will now link to your separate items. This will only apply to child SD records generated after your environment is updated to the new release. Avoid duplicates To avoid multiple listings of the same travel or transport service, we've added a Merge dialogue box. When creating a new item, the system will check for existing items with overlapping dates and the same:
If a user tries to add a duplicate of a travel or transport service that's been added as a separate service agreement item, the Merge dialogue box will:
The user can adjust the final allocation before merging. Comments included on a new item are not merged into the existing item. Users will need to edit the existing item to adjust or add comments. Scheduling services The new travel and transport feature doesn't change the way you schedule services. Users can continue to schedule the primary service. The separate travel and transport service agreement items won't be available for selection when:
Clients transitioning to PACE We've made a new Transitioned to NDIS PACE checkbox field available for you to add to your client record page layout. This field will be automatically ticked if the client has an NDIS service agreement with the PACE Plan option ticked. To find out how to add the field, check out our introduction to changing a client record layout article. For providers using our NDIA Integration Module, the Transitioned to NDIS PACE field was made available in a previous update to the module. The PACE Plan checkbox in NDIS agreements now affects which support category and service options show. When the checkbox is ticked, only PACE options are listed. When it's unticked, non-PACE Plan options show and PACE Plan options are filtered out. We've also included a count of open claims on the Item Summary table in NDIS extracts. As service bookings are not applicable to PACE Plan service agreements, we've modified our Lumary Settings. The Require Service Booking to Extract setting will not be applied to service delivered (SD) records on PACE agreements. System administrators can find this setting in Lumary Settings, under the Service Agreements tab. Open claims and financial systems We've updated the way open claims are handled when sending NDIS extracts to financial systems using the following buttons:
When successful claims are sent to financial systems using these buttons, open claims will be excluded, along with errors. If extract items for open claims are then marked with a claim status of Success, these buttons can be used again to send successful claims that haven't already been sent. It's important to be aware that:
Contract Insights dashboard We've improved the Contract Insights dashboard and related fields to improve accuracy and clarity. Committed amounts shown on the Contract Insights dashboard and service agreements now:
We've also improved the This Month's Service Deliveries by Claim Type graph on the Contract Insights dashboard. The breakdown now groups service delivered (SD) records by child SD record types as well as by claim type. Extracts We've improved the Lumary Extracts page for providers who have a large number of extract records. The Previous Extracts section will now only list the most recent 1,000 extracts for the extract type and date range selected. This prevents an error that was occurring for extract types and date ranges that include more than 1,000 records. 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 - Advanced | Contacts | Transitioned to NDIS PACE | Read, Edit |
Service | NDIS Plan Type | Read, Edit | |
Service Classification | Read | ||
Lumary - Basic | Contacts | Transitioned to NDIS PACE | Read |
Service | NDIS Plan Type | Read | |
Service Classification | Read | ||
Lumary - Standard | Contacts | Transitioned to NDIS PACE | Read, Edit |
Service | NDIS Plan Type | Read | |
Service Classification | Read | ||
Lumary - Extracts | Extract Item | Sent to financial system | Read, Edit |
Lumary - Incident Capture and Management | Corrective Actions | Related Incident | Read, Edit |
Lumary 21 minor release 2 |
Available from: 31/1/2024 Version: 21.46 Lumary 21 minor release 2 has been deployed to production environments. We've added improvements for:
We've also included updates to permission sets to support the rollover functionality and planned future features. This release requires Skedulo AU Healthcare v1.241 or later. If you're using Skedulo, the support of new features requires at least this version. We've fixed issues so that:
We've also fixed an issue with planned services on Beds Calendar bed allocations. Planned services will now still be viewable for service agreements where:
This was previously displaying an error. We've added the Case Notes, Rates and Service Agreement Item tabs to the Lumary package. This means that if you were using custom tabs for these objects, your users may experience a change to their visibility. To make the updated Case Notes and Rates tabs available to users, we've added them to the Advanced, Basic and Standard permission sets. Users can follow the steps in our navigation bar article to add these tabs to their nav bar. Providers using custom or cloned permission sets may need to add these permissions to those sets. We've listed the settings in the table below. If you need help with permissions for these tabs, please submit a support request. Tab permissions We've updated tab settings on objects on the following permission sets. If you have custom or cloned permission sets that include these objects, we recommend that you add these permissions. |
Permission set | Object | Tab setting |
---|---|---|
Lumary - Advanced | Case Notes | Available |
Rates | Available | |
Lumary - Basic | Case Notes | Available |
Rates | Available | |
Lumary - Standard | Case Notes | Available |
Rates | Available |
Incident management We've added new features for disability providers to record and manage incidents and feedback. This includes easy-to-follow interfaces to guide users through reporting and management processes. Users can use this feature to:
Users will need access to:
To get access to this new incident management feature, submit a support request to our Customer Success team. If you require customised notifications and/or alerts for the incident management feature, reach out to your Client Outcomes Manager. Service agreements We've provided a service agreement item calculator. When you create service agreement items, you can calculate quantity and total values based on a recurrence pattern. Find out how to calculate a quantity using recurrences. We've also continued to improve the service agreement rollover functionality. As part of rolling over an agreement, you can now move future scheduled services to the new agreement. Find out how to move future scheduled services to a new rollover service agreement. Rollover has been made available for other type service agreements. We've also replaced toggles with checkboxes for some options. Skedulo integration We've changed the way client summary PDFs attach to job records. If you've set up the PDF to attach to jobs, PDF files will now only attach to jobs scheduled within the next 7 days that are not cancelled or complete. This helps providers avoid hitting data limits by reducing the generation of unnecessary records. Find out where to check if your environment is set up to attach PDFs to jobs. For aged care providers scheduling Skedulo jobs, we've also improved the logic used to find available line items. This was previously preventing users from linking jobs to some line items. Permission sets We've made updates to field permissions on the permission sets in the following table. The Contact Type field permissions have been included to support future functionality. If you have custom or cloned permission sets that use the Contacts object, we recommend that you add these permissions. The Gender Detail field permissions have been included to support future functionality for DEX extracts. |
Permission set | Object | Field | Permissions |
---|---|---|---|
Lumary - Advanced | Contacts | Contact Type | Read, Edit |
Service Agreement Item | Rollover Service Agreement Item | Read, Edit | |
Lumary - Basic | Contacts | Contact Type | Read, Edit |
Service Agreement Item | Rollover Service Agreement Item | Read, Edit | |
Lumary - Standard | Contacts | Contact Type | Read, Edit |
Service Agreement Item | Rollover Service Agreement Item | Read, Edit | |
Lumary - Client Session | Service Agreement Item | Rollover Service Agreement Item | Read |
Lumary - Extracts | Extract Item | Gender Detail | Read, Edit |
Lumary - Site Guest | Service Agreement Item | Rollover Service Agreement Item | Read, Edit |
The following permission sets have been updated to provide access to the Apex classes listed. |
Permission set | Apex Class Access |
---|---|
Lumary - Advanced | enrtcr.TransferAppointmentsController |
Lumary 21 minor release 1 |
Available: 1 November 2023 Version: 21.20.4 Our first minor release for Lumary 21 is now available in production environments. We've added improvements for: NDIA PACE transition Claims for NDIA Plans on PACE may return a status of OPEN to show that the NDIA is still assessing the claim. To help providers manage open claims, we've added an Open Claim status to the Claim Status field on:
When using Process Results to upload NDIA results files, this status will be set on EXI and SD records for claims that return with an OPEN status. Find out more about the NDIA's OPEN status. We've also added a PACE Plan checkbox field to NDIS service agreements (SA). When this is ticked on NDIS SAs, a PACE badge will appear in the banner on agreements and on the Contract Insights tab. Get updates about the transition to PACE on our live PACE transition updates page. PACE permission set changes We've updated the following permission sets to provide access to PACE-related objects and fields. |
Permission set | Object | Field | Permissions |
---|---|---|---|
Lumary - Basic | Contacts | Transitioned to NDIS PACE | Read |
Lumary - Advanced | Contacts | Transitioned to NDIS PACE | Read, Edit |
Lumary - Standard | Contacts | Transitioned to NDIS PACE | Read, Edit |
NDIS extracts Due to PRODA restrictions that limit filenames to 20 characters, we've changed the filename format for NDIS extracts. The filename now includes the extract name instead of the date and time. Service agreements We've updated the service agreement (SA) rollover feature with:
Agreements with a Rollover status will now auto-generate SD records for agreement items that are:
As we work through these changes, rollover is temporarily unavailable for other type service agreements. We're working on bringing rollover back to this type of agreement soon. We've updated our rollover article to include these changes. We've also made improvements so that:
Xero and MYOB integration For providers with Xero integration, the Reference and Description fields on invoices can now show additional information. By default, the Reference field contains the client name and NDIS number. We can add values to both this and the Description field. For providers using MYOB extracts, we can add values to the invoice Description field. If you'd like to add values to any of these fields, reach out to our Customer Success team. |
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.