New article
Recently updated
Ideagen Maritime Safety 1.21.2 release notes
Who is this article for?
Administrators who are considering implementation of Ideagen Maritime Safety 1.21.2.
No elevated access or permissions are required.
This article outlines the changes made to Ideagen Maritime Safety in release 1.21.2, which is available to be scheduled for deployment from 16 March 2026.
Please contact your Ideagen Maritime Safety representative for deployment assistance and configuration requirements.
1. Fixes
| Number | Description |
|---|---|
| 1115872 | Fixed an issue where Work Permit takeover signature timestamps were always shown in UTC instead of in the time zone of the person who signed. |
| 1216699 | Fixed an issue where the Crew Member Details tab was not enabled for Third Party persons involved in Personal Injury with Medical Treatment/Record events; the tab is now available when the person type is set to either Crew or Third Party for clients with the Injury/Illness wizard enabled. |
| 1239182 | Fixed an issue where the system allowed users to transition events to a new status without validating the “Direct cause” and “Returned to Work” fields in the Maritime Safety module. |
| 1277441 | Performed a request to remove the "Other" option, including the "Description of Event Location Group" field, from the Personal Injury Event form for Carnival. |
| 1292156 | Fixed an issue with the Person Type field to reflect the correct value and have it appear in the People Involved Log rather than the Event Log. |
| 1299654 | Fixed an issue where the Event Deck Location and Event Location On Deck fields in the Hazard Observation template remained enabled when the Event Location was set to Ashore; these fields are now automatically disabled when Ashore is selected. |
| 1303975 | Fixed multiple critical issues with the Risk Assessment workflow. Resolved the "Publish Risk Assessment Template" post-transition action not functioning properly in Operations. Corrected Risk Assessment Number (RAN) formatting to include the required "V" suffix when Risk Assessments are published from Onboard to the Library. Fixed duplicate Risk Assessment entries appearing in the Library when Risk Assessments were published from Shoreside after adding additional ships. Added Risk Assessments to the recent category in the Global Search box for easier access. |
| 1310038 | Fixed an issue where users sometimes received an “Access Denied” error when reassigning events; permissions are now updated only after the reassignment redirect completes, preventing this error from occurring. |
| 1313711 | Fixed an issue where the Import Equipment page failed to display Label and Type values for existing equipment records; these fields are now correctly populated when viewing imported equipment. |
| 1313935 | Fixed an issue where users with passwords containing the + symbol could not log in or update their own Permissions/Roles/etc without being logged out; passwords with + are now handled correctly during login and profile updates. |
| 1315475 | Fixed an issue where MVAS users could not re-open closed events, even when they had the appropriate roles and the “Re-Open Event” permission. Fixed an issue where MVAS users were unable to request an Investigation because the system incorrectly required the subtype field, which is only used by Carnival. |
| 1316139 | Fixed an issue where the Booking/ID Number field was marked as required but remained disabled for Third Party persons involved in Personal Injury With Medical Treatment/Record events; the field is now enabled so users can enter the required value. |
| 1317065 | Fixed an issue where the Personal Injury with Medical Treatment/Record custom workflow in Staging did not respect the configured conditions for transitions (for example, when Person Type = Passenger and Calculated Injury Severity = Minor); workflow transitions now correctly follow the defined conditions. |
| 1319619 | Fixed an issue where the “Calculated Injury Type” field in Report Builder sometimes showed blank or incorrect values instead of matching the Primary Injury Type. |
| 1321787 | Fixed an issue where the Calculated Event Location field in Report Builder did not correctly evaluate the configured table rule logic, resulting in inaccurate or missing calculated values; the field is now derived using the same calculation approach as other calculated fields. |
| 1321870 | Fixed an issue where the Timeline for custom workflow events showed the assignee role from the previous status instead of the new status after a transition. |
| 1324186 | Fixed an issue where the Department field in Report Builder exports was empty for events even when the field was required and populated in the event, causing missing department values in reports. |
| 1324538 | Fixed an issue where multiple Injury/Illness Wizard v3 fields were not correctly reflected on the Medical Report for MSC. |
| 1326937 | Fixed an issue where Report Builder showed duplicate Medical Report subcategories under the Events category. |
| 1327873 | Fixed an issue where information entered in the Crew Member Details tab for Third Party persons in Personal Injury with Medical Treatment/Record events was not being saved; these details are now correctly retained after saving. |
| 1331794 | Fixed an issue where the Title and Description fields were blank when starting a new revision of a Risk Assessment template, requiring users to manually copy this information from the previous version; these fields are now automatically carried over to the new revision. |
| 1336621 | Fixed an issue where the First Officer Onboard field on Ideagen Maritime Management reports displayed the Security Officer instead of the actual First Officer; the correct First Officer is now shown in this field. |
Features and fixes listed in this release were tested with Google Chrome 145.0.7632.117 (64-bit) and Microsoft Edge 145.0.3800.82 (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.