Fatigue360

New Features & Improvements

Monthly Competency Expiry Email can now be sent to staff ahead of the expiry of competency records held in the system. This is enabled via a new setting that specifies how many days before expiry the monthly email should account for.
On-Call Module added to Fatigue360, allowing logging of periods when staff are expected to be on-call. When staff are recorded as on-call and are also rostered, the on-call period is shown on the shift sidebar. This module is off by default and can be enabled under the Miscellaneous section in Settings. (Note: This has no bearing on the feature within the Fatigue360 App).
Added the ability to filter the roster view by event type.
Minor timeline improvements to reduce rendering lag on the On Shift, Staff, Event, and Timeline views for large events. Items (backgrounds, shifts, events, etc.) are now updated in a single batch on data load.
Project dropdowns in the Event & Timeline Filters now load results via search instead of a full list.
Added new setting to control whether leave comments are sent down to the App.
Added a new setting to toggle whether auto-set events/shifts are automatically accepted/confirmed.
Added a new option on the Shift Timeline to change the order of data shown on the shift, allowing shift times or role to be prioritised.
Supplier name is now displayed for client shifts populated by a supplier.

Fixed a bug where the time-out of an actual was being replaced with the planned shift time in clause calculations.
Fixed a bug where users were unable to override Level 1 and Level 2 exceedances.
Fixed shift issue class not showing the correct severity when overrides are mixed.
Fixed override warning buttons appearing on shift actuals before they were created.
Ensured red-flagged people are now flagged on supplier shifts as well as normal shifts.
Fixed delete button visibility so it is only shown to users with the risk assessment permission.
Fixed a bug where sub-event blocks weren't cleared after deletion.
Fixed a bug where resetting the timeline would clear the pill order.

Users can no longer accept or reject a shift that is cancelled or marked as Did Not Attend.

Dropdowns for Companies, Cranes, Gates, and Laydowns are now ordered alphabetically.
Gates and Laydown areas can now be deleted when there are no future bookings.

Fixed a bug where the permission set wasn't applied correctly when changing organisations

Major expansion of Lone Worker functionality: Added a dedicated Lone Worker section to the event page, new API endpoints for the mobile app, a Lone Worker Automated Report, and options within requirements to allow Lone Workers and select an emergency contact.
Added push notifications for updated shifts, missed shift sign-in, and shift sign-out reminders (30 minutes prior).

Fixed "Last Seen At" on the Fire Register to fall back to the worksite field when the access zone name from the device log is unavailable.
Fixed an issue where vehicle export would fail.
Fixed an issue where large register import files could fail to load.
Fixed a bug where induction emails were queued for person records with no email address.

Facial Recognition Gateways can now be configured to automatically move to the next event when the current event finishes.
Added PIN code support as an authentication method, as an alternative to biometrics.
Added capture of automated DNSO events, including a reason field in the report builder.