Release notes

Available from 12 August 2025

Improvement

Change “+” button location in Personal Profile section

In version 5.18.1, we have made a highly requested user experience enhancement by repositioning the ‘Add’ (+) button to the top of the table across all the applicable sections under Personal Profile- improving user experience.

Previously, users managing large lists (like 50+ CCPs or procedures) had to scroll to the bottom repeatedly to add new entries, with the page reverting to the top after each action. The ‘Add’ button is now clearly positioned at the top of the following tabs: Roles, Workgroups, Competencies, Compliances, Procedures, Training Events, and Attachments.

For example, within the Personal Profile > Workgroup and Personal Profile > Procedure sections (see screenshots), the ‘+’ button is now easily accessible at the top-left of the table.

Fixes

One-way flight bookings now correctly trigger double booking warnings

We have addressed an issue where committing a workflow with a one-way flight booking triggered a system error instead of a warning about a potential double booking. The system was not handling null return flight values correctly during validation. It now detects overlapping flights as intended and displays a warning to the committer without failing unexpectedly.

Action-required filter now excludes committed and cancelled workflows

The “Only Requests That Require Action” filter on the Search Workflow Requests page was incorrectly displaying workflows that were already Committed or Cancelled. This behaviour has been corrected so that only active, actionable requests are returned. Workflows in Draft, Committed, Cancelled, or Declined status are now appropriately excluded from filtered results.

Commit process no longer fails when ‘ChangedBy’ is missing

Addressed an issue in +Process where workflow commits could fail if the associated person record had an empty “ChangedBy” value. This scenario caused unexpected exceptions due to strict validation. The system now handles these cases gracefully, allowing commits to proceed even if audit fields are missing or incomplete.

Duplicate notifications prevented when processing high volumes of scheduled reports

An issue was identified where restarting the scheduler in environments with a large number of daily scheduled reports (typically 40 or more) could result in duplicate notifications being sent. This has now been corrected. The system reliably handles bulk report processing without generating duplicates, even under high load conditions.