7.20.4.1

Clarive 7.20.4.1 Release Notes¶

Release date: September 16, 2026

We're pleased to present our new patch release of Clarive 7.20.4.1 with some important features and bugfixes:

Improvements and issues resolved¶

[FIX] #4017 Error when adding users to a notification¶

Fixed several problems when setting up the recipients of a notification. Recipients selected for the CC and BCC carriers were being written back into the TO carrier instead of their own, so users added to CC or BCC could end up misplaced or lost when the notification was saved. Each carrier now keeps its own list of recipients.

Empty entries are also no longer stored: blank values coming from the recipient fields, owners, emails, actions, roles and users lists are now discarded instead of being saved as empty recipients. In addition, trying to save a notification without selecting any recipient now shows a clear validation message asking for at least one recipient, rather than silently saving an incomplete configuration. Pop-up messages were also corrected so that error notifications are displayed with the proper error styling and always appear above modal windows.

[FIX] #4021 Editing a scheduler entry raises React error #130¶

Fixed an error that appeared when opening a scheduler entry for editing. The "Max run time (seconds)" field was declared with an unknown field type, which caused the form to fail while rendering and surfaced a React error instead of the edit form. The field now uses the correct numeric input type, so scheduler entries open and can be edited normally.

[FIX] #4024 When modifying a scheduler entry the form fields are reset¶

Fixed a problem where the values typed into a scheduler entry form could be cleared while the user was still editing. The form was resetting its fields on every re-render, so changes made in an open form could be discarded before saving. The fields are now reset only when a different entry is actually opened, so the values entered while editing are preserved and switching between entries still loads the correct data.

Ready to upgrade?¶

Just follow the standard procedure for installing the new version. Click here to get it from our Install page.

Acknowledgements¶

Join us in our Community to make suggestions and report bugs.

Thanks to everyone who participated there.