New article
Recently updated
SeaEvent 1.20.1 - Release Notes
Who is this article for?
Administrators considering implementation of SeaEvent 1.20.1.
No elevated access or permissions are required.
This article outlines the changes made to SeaEvent in release 1.20.1 which is available to be scheduled for deployment.
Please contact your SeaEvent representative for deployment assistance and configuration requirements.
Release Date: November 17, 2025
1. Features
1. (SE-7230) Signature Component for Forms
SeaEvent now supports digital signatures on forms, enabling users to create and sign documents directly within the application.
1.1 Form Editor - Signature Configuration
Administrators can now independently configure signature fields in fillable PDF forms without requiring support assistance. When a PDF with signature fields is uploaded, the system automatically detects these fields and allows configuration through the forms editor.
1.2 Signature Type Selection
When mapping signature field, administrators can designate the signer role or rank as:
- Roles
- Author
- Editor
- Assignee
- User Fields*
- Captain
- Staff Captain
- Security Officer
This allows forms to specify which role or position "should" be authorized to sign specific fields. The name selected here will appear below the signature field on the form, letting the user know who should sign.
*Note: If a user field from your legacy form does not appear as an option when mapping signature metadata, contact support to request that field be added to the available options.
1.3 Signature Metadata Mapping
For each signature field, administrators can optionally map form fields to capture:
- Signed Date and Time
- Signer Name
These mapped fields are automatically populated when the form is signed.
1.4 Digital Signature Capture
Users completing forms can now digitally sign using:
- Mouse or touchscreen input
- Physical signature pad hardware
When users click "Add Signature," a modal opens allowing them to draw their signature, with the current timestamp automatically captured.
1.5 Signature Management
- Signatures can be deleted and re-signed if needed before form finalization
- "Continue Editing" banner appears after signing, allowing users to complete remaining form fields
- Signatures become permanently locked once the form is finalized (printed, downloaded, attached, or emailed)
1.6 Draft Behavior
Forms saved as drafts preserve all field data but exclude signatures, ensuring signature validity. Signatures must be recaptured when returning to complete a draft.
1.7 User Benefits
- Streamlines incident and safety form workflows with digital signatures
- Clearly defines signing authority with role-based signature types
- Eliminates dependency on support for signature configuration
- Creates automatic audit trail with timestamps
- Maintains document integrity with post-signature locking
2. Bug Fixes
| Number | Description |
|---|---|
| 1059834 | Fixed an issue where the "Forgot Password" function could send password reset emails to the wrong recipient if the user was not listed on the vessel manifest. The update now ensures that only users present on the manifest can request a password reset, displaying an appropriate message if the user is not found, and preventing misdirected emails. |
| 1084845 | Fixed issue that caused persistent “Edit session about to expire” warnings to appear for Hazard Templates, even when no further edits were made. This behavior is now consistent with other modules. |
| 1088510 | Fixed an issue where drop-down menus would detach from their original position and move along with the page when scrolling. Previously, if a drop-down menu was open and the user scrolled the page, the menu would incorrectly follow the scroll movement instead of remaining anchored to its field. This update ensures that all drop-down components stay properly attached to their respective fields during page scrolling, improving the overall user experience. |
| 1088879 | Fixed an inconsistency in the Add Attachment feature where the drag-and-drop upload did not support the same file types as the standard file upload (Browse) option. Previously, certain file types (such as MKV) were rejected when using drag-and-drop but accepted via Browse. The MIME type configuration has now been unified, ensuring both upload methods accept the same file types as defined in the global configuration. |
| 1100634 | Fixed a cosmetic issue in the Work Permits module where required fields did not immediately display the red asterisk :yellow_star: indicator. Previously, some required fields would only show the asterisk after certain updates were made to the Work Permit, even though no conditions were configured for those validations. With this update, all required fields now consistently display the red asterisk as soon as the Work Permit is created, providing clear guidance to users on which fields are mandatory. |
| 1103296 | Fixed an issue where documents marked as non-printable in the Public Documents Library could still be printed or downloaded using browser functions such as Ctrl+P or the right-click menu. With this update, non-printable documents are now properly protected, preventing users from bypassing print restrictions via browser print or save as PDF features. This ensures that document permissions are consistently enforced across all access methods. |
| 1104010 | Fixed an issue where the Download Users Report in the Administration module only included Event Roles, omitting other important role types. With this update, the report now correctly includes Work Permit Roles, Document Roles, Hazard Roles, and Risk Assessment Roles. This ensures that all relevant user roles are accurately reflected in the exported report, providing a complete overview for administrators. |
| 1104675 | Updated the password reset process for Onboard Users attempting to access the Operations site. Previously, when an Onboard User requested a password reset code via the Operations site, the system incorrectly displayed a success message even though no email was sent. With this update, the system now displays an error message "If the information provided matches an account, you will receive a reset link by email." when an Onboard User—who is not on a ship manifest—attempts to request a password reset code from the Operations site, providing clear feedback and preventing confusion. |
| 1107271 | Fixed a cosmetic issue where the Event Details tab would briefly appear highlighted in red when opening certain events, incorrectly indicating missing data. This occurred intermittently in both production and testing environments, especially for Personal Injury Events. The underlying error handling has been improved to prevent the tab from being flagged red unless there is actual missing data, ensuring a clearer and more accurate user experience. |
| 1107419 | Fixed a cosmetic issue in the Events module where, for events created using the Workflow Editor, the Assignee was listed twice in the Event History after a status change. With this update, the Event History now correctly displays a single entry for the Assignee update, ensuring accurate and clear event records for users. |
| 1117077 | Fixed an issue where users were incorrectly prompted with a warning about losing unsaved changes when leaving a form, even if no changes had been made. With this update, the warning will only appear if there are actual unsaved changes, ensuring a smoother and less confusing user experience. |
| 1119499 | Fixed an issue where on the SeaEvent Operations Global Search results page, upon hovering over the event description in the results, the system was displaying an HTML code instead of the expected tooltip. |
| 1120619 | Fixed issue that prevented deselected vessels from being properly removed when saving changes in the configuration. Previously, vessels remained selected even after being unchecked and saved. |
| 1154284 | Fixed an issue where the signature on Work Permits displayed empty parentheses instead of omitting the rank when a user with a ‘Manager by Profile’ designation did not have a rank assigned. |
| 1161580 | Fixed an issue where attempting to approve a Risk Assessment resulted in an error. With this update, Risk Assessments can now be approved successfully without encountering errors, ensuring a smooth approval process for users. |
| 1201062 | Fixed an issue where the Medical Report section displayed data for certain fields even when those fields were not completed in the event. The report builder now only displays data for fields that have been filled out, ensuring accurate and relevant reporting. |
| 1212634 | Fixed an issue where the "Revision No" column in the Workflow Editor did not sort revision numbers correctly. Previously, revisions were sorted as strings instead of numeric values, resulting in incorrect order. Now, revisions are properly sorted by number, with the most recent revision displayed at the top by default. |
| 1217228 | Fixed an issue where, when viewing the Persons Involved wizard in Events, the application would incorrectly auto-select the last person involved instead of the first. With this update, the wizard now automatically selects the first person in the list, ensuring a more intuitive and consistent user experience when reviewing involved persons in custom workflow events. |
| 1217231 | Fixed an issue where in the Workflow Module, under the Events tab, the system was not display int correct label for Crew, Passenger, Third Party or Other for Personal Injury events with the Persons Involved wizard included. |
| 1220841 | Fixed an issue where voyage activation could be interrupted if errors occurred while parsing itinerary data, causing the process to stop and preventing the next voyage from being activated. Voyage activation now continues regardless of errors in fetching cruise or itinerary information. |
| 1222254 | Fixed an issue where enabling a large number of Event Roles on a profile caused users to be unable to log in due to a "QuotaExceededError: Setting the value of 'user' exceeded the quota." Users can now enable all available Event Roles without encountering this error. |
| 1222886 | Fixed an issue where newly created custom fields with the "Corrective Action" class could not be added to workflows, as they were not visible in the required fields selection. The system now correctly displays fields associated with the selected Type in the workflow before changes are saved. |
| 1222994 | Fixed an issue where the order of workflow actions did not match the order displayed in the event's drop-down menu after rearranging transitions in the Workflow Editor. |
| 1227611 | Fixed an issue where users without the "Re-Open Event Report" permission were able to reopen Custom Workflow Events. Now, reopening a Custom Workflow Event requires both the "Re-Open Event Report" permission and the appropriate Event Role for the specific transition and event type, ensuring proper access control. |
| 1229519 | Fixed an issue where history logs for work packages were not displayed in the correct chronological order. |
| 1236870 | Fixed an issue where the Crewmember Details tab was enabled for Guest Injury events if a Crew Member was listed as any person involved, even when the injured person was a Guest. The tab will now only be enabled when the injured person is a Crew Member, ensuring consistent behavior with legacy workflows. |
| 1256010 | Fixed an issue where users were unable to save an Event when the "Corrective action" field was marked as "No," resulting in a message that all required fields must be completed, even though all fields were filled. |
| 1264352 | Fixed an issue where two fields were not saved after submitting the event. |
3. Browser Compatibility
The features and fixes listed in this release were tested with:
- Google Chrome version (142.0.7444.135)
- Microsoft Edge version (142.0.3595.76)
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.