UPDATES MADE
APPOINTMENT MANAGEMENT |
- The migration Id is cleared from a session when deleted from easyemployer and the status of the session is set back to draft.
- When the Session is not a group Session (only 1 client attending) the actual time will be charged based on the Session actuals not based on the clients scheduled time.
- The Service Delivered records are created using scheduled time if the planned services delivery method is not Workers Actual.
- For a Group Session, when Session actuals are outside the Client Attending times. All planned services that have a service delivery method that is Worker Actual will not be charged and the Client Appointment will have a cancellation reason of "Insufficient worker Attendance".
- In a group session where there's a client not attending the full length of the session, you can now set the delivery method to 'workers actual time". This will mean the client will only be charged for the time the "Session Actual Time" overlaps the time the client is scheduled to attend.
- Status field added to Client Appointment object which shows Session Status unless Cancellation Reason is not empty, then Status should be 'Cancelled'.
Refer to Session
|
MOBILE APP FOR SUPPORT WORKERS |
- All data that has been loaded on the app prior to going offline will remain when closing and opening the app.
- Changes that are made are stored in the online database.
- If the user logs out data will be synced up prior to this.
|
ENQUIRIES UPGRADE |
- The enquiry page is more dynamic and consists of a new simplified page layout and a new lightning record page.
- Automated to create necessary records when an enquiry is completed.
- Additional fields have been added to the record and page layout to make sure all the necessary information is captured when an enquiry comes in.
Refer to Enquiry Pathway
|
FINANCIAL EXTRACTS |
- MYOB extract modified to exclude 'Block Grant' service delivered records.
- Scheduled service delivery invoice process adds records to carts based on funding manager.
Refer to Finances |
BEDS CALENDAR |
- Able to pick from configurable lists of Site and Bed Amenities.
- Accommodation Type options of SIL and STA.
- Information is stored against a contact record.
- Matching Information is stored against Bed and Sites.
- Ability to identify emergency beds.
- Global picklists created to ensure values on Bed and Site are consistent.
- A selection has been added on the planned service Billing Method to charge the upcoming amount for a planned service when it is added to a bed. Billing Method is a picklist with values "Pre-Charge" and "Post-Charge".
- Ability to filter on the Beds Calendar for the Short Term accommodation needs for specific groupings.
- Ability to blocklist a contact from another client to identify that they shouldn't be placed together.
Refer to Booking Beds
|
SKEDULO INTEGRATION
|
- When a Job Allocation has travel entered then the Service Delivery record will be created with the appropriate travel on the service delivery records only using rules for travelling to an appointment.
Refer to Skedulo Integration
|
SERVICE AGREEMENT |
- We have replaced original fields to support future cancellation options.
- A batch process to run and migrate the service booking details into the new object.
- Able to set the day of the month to auto-deliver a service from the options available, such as the option "first Thursday of the month".
Refer to Individual Service Agreements
|
NDIS CANCELLATIONS
|
- Field added to Service Booking object to capture how many hours of therapy services have been cancelled for the Service Booking.
|
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) have been 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.