Skip to main content

8.1.2 Changelog

Written by Sean Stofberg

Features

  • Cora Chat now sends a message when you press Enter; Shift+Enter adds a new line.

  • Added a Restore to option when reversing a claim rejection, so the claim can be returned to Submitted, Pending or Draft instead of always Submitted.

  • Added a clear button to the sidebar Quick Search once a search has been typed, and to the Register Templates search.

  • Added a public holiday marker to public-holiday days in Timesheets and the timesheet PDF, explaining whether the day's hours were paid at the public holiday rate or, for contracted paid leave, at the shift's own rate.

  • Emailing a claim is now recorded in the claim's Activity timeline, including who it was sent to.

  • The Storage button is now available on the client edit screen as well as the client view, and a client's default storage folder is created on first use.

Improvements

  • When approving leave, every impacted shift now defaults to the request's leave type; a shift that already carries a leave type can be set to keep it, and it is still cancelled and replaced with an open shift unless its role is excluded from open shifts. Ignore is no longer offered on shifts with no leave type.

  • Changing a shift after its leave request is approved is now a Roster edit: the Mark as worked button has been removed, the leave request and the timesheet PDF direct you to the shift in the Roster, and a changed or cleared leave type is recorded in the shift's history with a reminder to deduct the balance by hand.

  • The leave request view now shows the leave type on each impacted shift, Keeping existing leave and Left worked counts, a No Leave Type badge where none is set, and public holiday status under the date; once a request is approved, its guidance describes what approval did rather than what it will do.

  • The leave approved email now explains that covered shifts have been cancelled and replaced with open shifts, including those that kept an existing leave type, and the Open Shifts description in Leave settings explains that the excluded roles apply to every shift an approval cancels.

  • Leave, roster and finance wording now follows the pay rules: paid leave counts only on contracted hours, leave owns its public-holiday hours, and the roster's Non-Contracted Paid Leave row is now Paid Leave Beyond the Daily Limit.

  • The Leave Hours summary on a leave request, and the finance notes that refer to it, are now shown only to leave approvers and finance users.

  • The Roster no longer shows the "Shifts inside approved leave" warning banner, which was ambiguous and ran an extra check on every roster load.

  • Roster template saves now clamp the period to the six-week maximum instead of refusing the save, template messages and empty states describe what actually happens, and a save or apply refused because of participant access names the affected shift by day and time.

  • In the interaction wizard, the Recommended shift section now sits in the Billing step, lists only shifts that overlap the interaction's own start and end time, and reloads when those times change.

  • Custom storage folder links for a client are now checked when saved, rejecting links to files, deleted folders, or folders you cannot access.

  • Long template and author names in the Register Templates list are now truncated, with the full name shown on hover.

Bug Fixes

  • Fixed PDF downloads failing for NDIS Incident Reports completed on the earlier version of the form, with a clearer message when a form version cannot be exported to PDF.

  • Fixed leave over a sleepover night deducting the whole night from the balance instead of only the sleep-window hours it overlaps.

  • Fixed a sleepover's break being taken from the sleep window instead of the worked hours either side, which could pay the full sleepover regardless of the break.

  • Fixed a leave shift's public-holiday hours being paid at the public holiday rate instead of the shift's own base rate; leave now takes priority over an overlapping worked shift on every day, public holidays included.

  • Fixed contracted public holidays being force-ignored on leave approval; they now convert like any other day.

  • Fixed a shift clipped by leave losing its afternoon or night loading, attracting an inadequate-rest penalty, or having its break charged more than once.

  • Fixed leave shifts paying allowances.

  • Fixed the Leave Hours summary leaving out shifts that kept an existing leave type, and leave request public-holiday notes describing a shift that keeps a paid leave type as unpaid.

  • Fixed the weekend Annual Leave note on a leave request claiming an approval it had not checked, and continuing to appear after the request was approved or denied.

  • Fixed the leave weekend warning treating casual and contract staff as eligible for paid leave, and roster export employment codes now match the staff list.

  • Fixed leave approval skipping its confirmation when every affected shift kept its existing leave type, and the confirmation no longer says that zero shifts will be cancelled.

  • Fixed approving a leave request with shifts set to Ignore sometimes recording a converted shift as deliberately left worked, so it was missing from the Leave Hours summary and from Cora Chat's roster compliance check.

  • Fixed two leave approvals for the same staff member processed at the same time, or a roster edit made during an approval, being able to cancel the same shift twice or leave a shift both rostered and covered by a replacement open shift.

  • Fixed a leave request opened straight after another sometimes showing the previous request's status.

  • Fixed public holiday badges and notes disappearing from a leave request's shifts once the request was approved.

  • Fixed nine leave and public-holiday defects found in review, including roster and finance public-holiday parity, a tooltip hidden behind other elements, the timesheet PDF empty state and the weekend Annual Leave wording.

  • Fixed Cora Chat roster compliance checks reporting a shift as a leave conflict when another approved leave request already covered it, and shift lists showing times in your browser's timezone instead of the staff member's pay-calendar timezone.

  • Fixed number fields in Administration settings > Invoicing > Approvals and Claims rewriting or un-deleting values as you typed; fields can now be cleared while editing and are checked when you leave them.

  • Fixed breadcrumbs under Invoicing showing a Config suffix and lower-cased acronyms such as NDIS and KPIs, so they match the tab names.

  • Fixed the Void agreement action being available while the reason was empty.

  • Fixed two identical error toasts appearing when a claim send to Xero or by email failed.

  • Fixed draft agreements with an empty Terms field showing unsaved changes when nothing had been edited, and failing to save after the Terms field was cleared.

  • Fixed archived participants being offered in the Invoicing > Interactions client picker, while an interaction recorded before a participant was archived still shows that participant's name.

  • Fixed overnight roster template shifts previewing on two days in the roster grid, and template preview hours including sleepover and on-call time that the roster's own totals exclude.

  • Fixed roster template saves being refused for users who moved a participant already on the template to another staff member's shift.

  • Fixed a renamed roster template being applied to the same period twice without the duplicate warning, a second Apply click discarding the undo for the previous apply, and template undo deleting a draft shift whose allowances or interested staff had been changed.

  • Fixed organisation owners without an explicit roster role losing draft shifts and shift admin notes in roster views and exports, and admin notes being included in exports for users without permission to edit the roster.

  • Fixed the Xero customer list being marked as failed for the newly selected organisation after switching Xero organisations while a load was in progress.

Did this answer your question?