New article
Recently updated
SeaEvent 1.19.3 - Release Notes
Who is this article for?
Administrators considering implementation of SeaEvent 1.19.3.
No elevated access or permissions are required.
This article outlines the changes made to SeaEvent in release 1.19.3 which is available to be scheduled for deployment.
Please contact your SeaCare representative for deployment assistance and configuration requirements.
Release Date: 18th August, 2025.
1. Bug Fixes
| Number | Description |
|---|---|
| 1025893 | Resolved an issue in the SeaEvent Operations Event Details wizard where a COMMON.OTH error message was displayed for some field names, preventing users from saving or editing the event. With this fix, users can now save and edit events without encountering this error message. |
| 1052232 | Fixed an issue in the Workflow Editor where alert messages on free-text fields would repeatedly appear after every character typed, disrupting data entry. The system now displays the alert only after the first character is entered, and will not show it again unless the user deletes all text and starts over. This improves the user experience when working with field alerts in workflows. |
| 1068640 | Fixed an issue where the order of fields and tabs in the 'Summary Brick' did not match the order configured in the Event or Work Permit type. Now, when fields and tabs are reordered in the type configuration, the 'Summary Brick' will accurately reflect the same order after saving. This update ensures consistency between the configuration and the displayed summary for all types. |
| 1072050 | Fixed an issue where certain fields in the Forms module were not auto-populating data related to the vessel. This defect was caused by a recent code update that inadvertently excluded vessel data from being loaded. With this fix, forms will now correctly auto-populate all relevant fields as expected, improving data entry efficiency for all users. |
| 1073268 | Fixed an issue where Work Permit notifications sent to onboard users included incorrect shoreside URL links. With this update, notifications for work permits no longer contain links to the shoreside instance, ensuring users are directed only to the appropriate onboard environment as intended by the client. This change improves clarity and prevents confusion for onboard personnel receiving these notifications. |
| 1073345 | Fixed an issue in the workflow menu where not all condition rules were displayed when filtering for "Crime Against Person(s)" in Operation Production CCL. Previously, only 2 out of 17 expected condition rules were visible. With this update, all configured condition rules are now correctly shown, ensuring users have full visibility and accurate rule management. |
| 1074256 | Fixed an issue where deactivating a field used as a filter in Custom Reports would break the report, preventing users from editing or downloading it. With this update, deactivated fields and filters will remain visible and functional in the report builder. Deactivated fields are now highlighted in orange in the sidebar, and hovering over them displays a message indicating the field or filter is no longer available. This enhancement ensures uninterrupted access to reports and provides clear visual cues for inactive fields and filters. |
| 1082201 | Fixed an issue in the Event Workflow filters where check-marks did not accurately reflect selected values. Previously, after resetting filters, check-marks could remain toggled or disappear incorrectly, causing confusion about which filters were active. With this update, the check-marks now consistently display the correct selected values, ensuring users have clear and accurate feedback when applying or resetting filters in the Event Workflow. |
| 1087934 | Fixed an issue in the Work Permit Summary where multiple deck plans could be incorrectly displayed after adding, removing, and re-adding deck plan locations before saving. With this update, only the currently selected deck plan locations are shown in the summary, ensuring accurate and up-to-date information for users managing work permits. |
| 1097016 | Fixed an issue where the Import Accounts feature created accounts but did not add them to the ship manifest. This was caused by account creation messages not being replicated to the ship environment. The synchronization logic has been updated to ensure imported accounts are now correctly added to the manifest as expected. |
| 1098104 | Fixed an issue where the Shoreside Management Event Description field could not be saved on events using a custom workflow. Previously, users were unable to add new data to this field for new events, although editing existing data was possible. The update ensures that the field can now be updated as expected for both new and existing events using custom workflows. |
| 1100629 | Fixed an issue where conditions added to workflow validations in the Workflow Wizard were not being saved as expected. Previously, any conditions added to a validation would disappear after saving the workflow. The update ensures that conditions are now correctly retained when saving or updating workflow validations. |
| 1101096 | Fixed an issue where the "Assignee Required" option would not appear during a workflow transition if "Reason Required" was also enabled. Both options are now correctly displayed when configured together in transition settings. |
| 1103296 | Fixed an issue where onboard users were unable to print or download documents from the Documents Library or the external Public Library. The problem was caused by a hardcoded identifier in the public route, which prevented access to public or printable documents. The update ensures that users can now successfully print and download documents as expected from both onboard and public libraries. |
| 1104419 | Fixed an issue where the Events tab in the workflow module was not displaying all results, even when filters indicated multiple pages of events. The problem was due to the event-status-label being tied to legacy statuses, which prevented the UI from rendering new status badges correctly. This fix ensures that all relevant events are now displayed as expected in the Events tab. |
| 1105921 | Fixed an issue where custom fields in Task Notifications—specifically Task Comments, Task Update Comments, Task Summary, and Task Description—were not displaying any data in notification emails. This fix ensures that these fields now populate correctly when included in Task-related notifications. |
| 1110153 | Fixed an issue where users were unable to review and update Security Events in the Enterprise Events module due to multiple validation issues. This fix ensures that users can now process Security Events as expected. |
| 1110194 | The Ship Position field in the Personal Injury With Medical Treatment/Record event template is now required. Previously, this field was not mandatory, which could result in incomplete event records. With this update, users must provide a value for Ship Position when creating these events, ensuring more complete and accurate event data. |
| 1115289 | Fixed an issue in the Workflow Editor where attempting to change or disable a Validation on a Rule from a prior Workflow Revision would result in all validations for that workflow being duplicated each time the Save button was used, rather than updating the original validation. This fix ensures that edits to rules and validations in previous workflow revisions now update correctly without creating duplicate entries. |
| 1117685 | Fixed an issue where injury severity was incorrectly calculated for events involving fractures. According to reporting criteria, any fracture—except those involving fingers, toes, or teeth—should be classified as Major. Previously, the system did not apply this rule when the “General Body Region” was selected, resulting in some fractures being categorized as Minor. This update ensures that all applicable fractures are now correctly classified as Major, regardless of the selected body region. |
| 1118660 | Resolved multiple validation issues in the new Personal Injury event workflow. Previously, the Crewmember Details tab was active even when the injured person was not a crew member, and certain required fields—such as First Name and Family Name—were not recognized, causing validation failures. With this update, the Crew member Details tab is only active when the injured person is a crew member, and all required fields are now properly validated, ensuring accurate data entry and workflow behavior. |
2. Browser Compatibility
The features and fixes listed in this release were tested with:
- Google Chrome version (139.0.7258.67)
- Microsoft Edge version (139.0.3405.86)
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.