This release is the first to reflect Lumary's new naming protocol. Releases will no longer be associated with names like Hogan, but will now be indicated with whole and decimal numbered increments.
System administrators can now launch a process to synchronise data not related to sessions. This will include objects and records like employee, abilities, custom entities, availability and leave.
Shifts created, assigned and reassigned in easyemployer are now automatically integrated into the Lumary system.
|Invoice PDF generation|
Additional fields can now be selected for inclusion in invoice PDFs.
An option has been added to Lumary Settings to allow system administrators to enable users to create sessions in the past.
Minor bug fixes have been applied to resolve issues affecting:
Additional updates to this release are available with version 10.1, which applies fixes to:
- error messages in service agreement
- client profile pictures in the Client Summary PDF
- client record photo duplication.
Further updates have been applied to this release and are available with version 10.4, which applies fixes to:
- service delivery entry page sizes
- category support item codes in carts
- service delivery record creation dates when the record is created from a planned service
- site availability in the service delivery entry picklist when there are more than 50 sites
- ad-hoc service editability in a service delivery entry
- service booking migration and deletion of old records
- the updating of the funding manager account name in service agreements.
This update also a applies a fix to prevent the saving of incorrect rates in service agreements.
How and When These Features Become Available
Lumary will install the release package into your sandbox for a piloting phase period of 6 weeks. Your organisation’s primary contact(s) are notified of this sandbox upgrade approximately two weeks prior.
Following the sandbox period, the application upgrade will be automatically installed into your production environment, and the release will then be available to all users in your organisation. Communications will be made to primary contacts about the upcoming sandbox and production upgrades.
Consider communicating these changes to your users beforehand so that they are prepared.