New article
Recently updated
SeaEvent 1.19.2 - Release Notes
Who is this article for?
Administrators considering implementation of SeaEvent 1.19.2.
No elevated access or permissions are required.
This article outlines the changes made to SeaEvent in release 1.19.2 which is available to be scheduled for deployment.
Please contact your SeaEvent representative for deployment assistance and configuration requirements.
1. Features
The following updates have been made in the Admin section of Operations to support a clearer distinction between fields and wizards, and to streamline the configuration of event-related components.
1.1. Wizard visibility in Type tab
In Operations, go to Admin, then the Type tab. Under Wizards actions, all wizards are now visible, even if already migrated.
- Applies to Event Classes: Corrective Actions, Source Events, and Persons Involved.
1.2 Removal of Wizard names from Fields table
In Operations > Admin > Fields tab, the system no longer displays the following as field entries under the table:
- Corrective Action
- Source Event
- Persons Involved
Note: These items are now designated as wizards and no longer configured as standard fields.
1.3 New "Wizards" category in Applicable Class dropdown
In Operations > Admin > Fields tab > Fields Wizard, a new “Wizards” category has been added to the Applicable Class dropdown.
Under this category, the system displays:
- Corrective Action
- Persons Involved
Note: Source Event is intentionally excluded from this list.
1.4 Removal of Wizard components from Component dropdown
In Operations > Admin > Fields tab > Fields Wizard, under the Component field, the following components have been removed and are no longer displayed for any applicable class:
- Corrective Action
- Source Event
- Persons Involved
1.5. Subtab field clean up for Events Applicable class
When Events is selected as the Applicable Class in Operations > Admin > Fields tab > Fields Wizard, the Subtab dropdown no longer includes:
- Corrective Action
- Source Event
- Persons Involved
1.6 Removal of Wizards column from subtab Admin view
In the Subtab Admin section of Operations > Admin > Fields tab > Fields Wizard (when “Events” is the Applicable Class), the Wizards column has been removed from the interface.
2. Fixes
| Number | Description |
|---|---|
| 955483 | Fixed an issue where preventive actions implemented and assigned for an event were appearing empty in the system. This caused the details of the preventive action to be missing in the Tasks section of the event record. |
| 1050620 | Fixed an issue where in the SeaEvent Enterprise > Report Builder, some new field options were not displaying in certain filters as expected. |
| 1058577 | Fixed an issue where an unhandled error could occur in production environments, and where querying logs for newly created events resulted in the error message “Cannot access offset of type string in string.” These issues have been resolved to ensure stable event processing and reliable log queries. |
| 1069158 | Fixed an issue where multiple interconnected problems were affecting the Location on Deck field and the Heatmaps Dashboard, including:
|
| 1070625 | Fixed an issue where notifications were not being sent across workflows, with only Inactivity Warning, Reassigned, and New Draft Personal notification types being delivered as expected. This defect has been resolved to ensure all notification types are now correctly sent across all workflows. |
| 1073957 | Fixed an issue where filtering in the Report Builder by the name of the person involved resulted in empty First Name and Family Name fields. The fields for person involved have been reviewed and corrected to ensure names are displayed accurately when filters are applied. |
| 1078683 | Fixed an issue where the Description field for Technical was incorrectly required when the Port Logistic/Operations field was set to Other, instead of only when Technical itself was set to Other. This incorrect requirement prevented users from saving changes to these types of events. Additionally, the Technical field should only be enabled when the value in Reason for Deviation is set to Technical. The logic has been corrected to ensure proper field behavior and allow users to save updates successfully. |
| 1081070 | Fixed an issue affecting alerts linked to the “Reported to 3rd Party Authorities” field: Alert Deletion: Previously, users were unable to delete alerts associated with this field, causing usability challenges when alerts needed to be removed or adjusted. This has been fixed, and alerts can now be deleted as expected. Duplicate Alerts: Updating the field was incorrectly triggering the alert twice instead of once. This duplicate notification behavior has been resolved, ensuring alerts now trigger only a single, accurate notification when the field value is changed. |
| 1081613 | Fixed an issue where saving a searched Person Involved or Type of Involvement on Altercation events failed with an integrity constraint violation error: “1048 Column 'unique_code' cannot be null.” This defect prevented users from saving updates to persons involved in these events. The issue has been resolved to ensure proper handling and successful saving of person involvement details. |
| 1084045 | Fixed an issue where Report Builder results were displaying as [object Object] because the .name path was removed from the mongoField after editing a field in the Workflow Editor. This broken path caused reports using the affected field as a column to return incorrect or unreadable results. The issue has been resolved so that editing or updating a field no longer breaks the mongoField path, ensuring reports display data correctly. |
| 1086662 | Fixed an issue where fields from the Persons Involved module that were set as required through client-configured validations were incorrectly flagged as not belonging to the Security Event type or workflow, even though they were active for that event type. Additionally, validations for these fields continued to trigger even after they were deactivated, preventing events from being advanced. This defect has been resolved to ensure required fields from the Persons Involved module are correctly recognized by applicable event types, and that deactivated validations no longer cause blocking errors. |
| 1087374 | Fixed an issue where event links inside events were not accessible, preventing users from opening related events directly. This issue has been resolved to ensure seamless navigation between linked events within the system. |
| 1091721 | Fixed an issue where the calculated field “Injury Severity” was missing from events, both near the event type and within the event body. This issue was caused by logic errors in the calculated fields configuration, which also disrupted overall behavior of calculated fields. Additionally, the Person Type field could not be updated, resulting in multiple selected items with an empty input, preventing users from modifying or adding new conditions using fields from the Persons Involved wizard. The calculated field now appears correctly near the event type, and calculated field functionality has been restored. |
Features and fixes listed in this release were tested with Google Chrome 138.0.7204.50 (64-bit) and Microsoft Edge 138.0.3351.55 (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.