New article
Recently updated
Ideagen Maritime Safety 1.21.5 release notes
Who is this article for?
Administrators who are considering implementation of Ideagen Maritime Safety 1.21.5.
No elevated access or permissions are required.
This article outlines the changes made to Maritime Safety in release 1.21.5, which is available to be scheduled for deployment from 8 June 2026.
Please contact your Ideagen Maritime Health representative for deployment assistance and configuration requirements.
1. Fixes
| Number | Description |
|---|---|
| 1399548 | Fixed an issue where editing or adding a condition to a Custom Validation rule for Document Attached in the Workflow Editor would reset the selected Document Type, potentially affecting other entries in the same rule set. Fixed an issue where the Document Type specified on a Custom Validation for Document Attached was not evaluated correctly, causing the system to prompt the user to attach a file of that type even after a valid file was provided. Fixed an issue where only one Custom Validation for Document Attached was enforced when multiple validations were configured, instead of prompting for all required document types. Fixed an issue where publishing multiple revisions of a Workflow could cause all Custom Validations for Attachments to be ignored entirely. |
| 1418418 | Fixed an issue in the Workflow editor when modifying Conditions where the placeholder text for the Condition dropdown displayed an incorrect value. This could additionally result in Conditions being evaluated incorrectly, preventing an expected workflow transition. |
| 1427485 | Fixed an issue where email notifications failed when an invalid recipient address was included in the To/CC/BCC list along with valid recipients. Note that "invalid" refers to a email address that is correctly formatted but does not exist on the destination mail server. Notifications now skip invalid addresses and deliver successfully to valid recipients. This fix should be further validated in each Staging environment. |
Note: Features and fixes listed in this release were tested with Google Chrome 148.0.7778.217 (64-bit) and Microsoft Edge 148.0.3967.96 (64-bit).
While we strive to ensure compatibility, we cannot guarantee functionality with newer browser versions, as third-party updates may introduce changes that affect existing functionality as well as performance. For the best experience, we recommend using the tested versions or contacting support if issues arise with newer releases.