🛠️ Updates & Improvements 🌱

We are pleased to release several system improvements with this release. Please find below a summary of the latest additions.

🧮Total Unscheduled Hours on Dashboard showing a different amount compared with unassigned.

The Unassigned hours and the Unscheduled hours An update has been made to count all supports with a chargeby of Hour & Hours will add to the total on the dashboard. This was adjusted in the Coordinator Dashboard view as well.

📍Postcodes not showing on Participant overview screen

The Postcode field that was missing in the participant profile main screen has been re added.

✅Overnight Wake Up Button

A fix has been applied to display or not display the Worker app button as it was not deactivating when the setting was turned off. I now works as intended.

📅Worker App Leave request notification and settings

When a worker role was both Administrator and Worker and a leave request was submitted, it advised an email for this leave request was sent but it was not. This has been adjusted to ensure the communication is received.

📝Reporting Account Total Cost pdf issues for Participant Invoices

When printing to PDF there were a few formatting inconsistencies relating to blank pages and incorrect or missing data being cut off from the page. This has been address so the correct information is appearing with no additional formatting issues.

✅ Cannot remove a Worker Location

On the worker profile, when you removed the worker location and saved it, the location would still appear. This has been adjusted to work as required.

📲Broadcast SMS are not being received

The was an error with some Broadcast supports SMS’s not being received. A connection issue has been identified and resolved.

📝Some Core Funding Types not displaying on Reporting > Participants > Participant List Export

Certain Core Funding types were recognised as missing from the participant List Export. These fields have been re added to the report.

🧑Support Worker Incompatibility' instant popup issues

When a worker is identified and flagged as incompatible with that participant, a flag pops up alerting you to the issue. This was working only for grouped supports and not single supports. An update has been made to address this issue.