7.20

Clarive 7.20 Release Notes¶

Release date: June 12, 2026

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

Improvements and issues resolved¶

[ENH] #3721 Refactor repos plugin¶

The artifact browser backend has been migrated from the legacy ClaJS engine to native Perl, improving reliability and performance. Artifact search now queries files directly from disk rather than a MongoDB catalog, making results more accurate even for repositories that have not been indexed. Tree navigation and file viewing have also been fixed for local artifact repositories.

[ENH] #3725 Refactor admin plugin¶

The administration panel backend has been fully migrated from ClaJS to native Perl Catalyst, covering user, role, permission, project, config, scheduler, and system statistics endpoints. This improves stability and lays the groundwork for future enhancements to the admin area.

Administrators can now impersonate any user directly from the Users grid (requires the action.surrogate permission) to see the application exactly as that user sees it — including their permissions, available fields, and workflow transitions. An amber banner is shown throughout the session, and the original page is restored when simulation is stopped. During simulation, permission icons appear on topic fields showing which roles grant or deny access to each field.

[ENH] #3879 In-view edit fields¶

HTML-formatted text fields in topic view mode can now be edited inline without opening the full topic editor. Clicking on an HTML field activates a rich TinyMCE editor directly in place, allowing users to make quick updates and save without leaving the topic view.

[ENH] #3881 Improve topic editor load time¶

The topic editor now opens noticeably faster thanks to several backend optimizations: redundant database queries have been eliminated, revision history is fetched in a single aggregation pipeline instead of one query per revision, and resource list lookups use targeted field projections. Users working with topics that have long histories or many linked resources will see the most improvement.

[ENH] #3888 Remove GraphQL leftovers¶

All remaining GraphQL queries in the application have been replaced with standard REST endpoints, completing the migration away from the GraphQL layer. This affects dropdowns for Projects, Rules, Natures, Environments, Categories, Pipelines, Status, and Scheduler administration — users will not notice any change in behavior, but the application is now simpler and more maintainable.

[ENH] #3890 Global search in artifacts navigator¶

Users can now search for files across all accessible artifact repositories at once, without having to select a repository first. Search results include a Repository column so users can immediately see which repository each file belongs to, and clicking a result navigates directly to the correct folder in the tree.

[ENH] #3891 Add user in history field in personal reports¶

The status transitions history column in personal reports now shows the username of the person who performed each transition, alongside the date. For topics with older transitions recorded before this change, usernames are backfilled automatically from the activity log.

[ENH] #3893 Documentation update¶

The English and Spanish documentation has been updated to cover several features introduced in this release cycle: global artifact search, user in status transition history, the inline HTML editor for topic view, the permission details modal with role states, the report filter modal, job cancellation from the job log, and progressive dashboard dashlet loading.

[FIX] #3882 Save and new in new effort is closing the form¶

The "Save and New" button in the effort creation panel now correctly clears the form and keeps the modal open for the next entry, instead of closing the modal and discarding the new form state. The effort type selection is also properly reset on each new entry.

[FIX] #3883 Topics of disabled categories should be available for view if searched (#mid)¶

Topics belonging to disabled categories can now be opened and viewed when found via search or direct URL, instead of showing an error. At the same time, editing, deleting, changing status, and deploying are correctly blocked for these topics, and a warning banner is displayed at the top of the topic view to indicate that the category is disabled.

[FIX] #3884 Error en visualizacion de regla¶

Fixed a display issue in the rule editor where code editors (ACE) inside non-configuration tabs were not being resized correctly when switching between tabs or resizing the dialog window. The Profiles tab now also scrolls properly when its content overflows.

[FIX] #3885 Web server worker killed by segfault on nested _capture_tee¶

Fixed a crash that could kill a web server worker process when output capture was nested (e.g., a job running inside another job or monitored command). The inner capture now runs through the parent's existing capture layer instead of adding a new PerlIO tee layer, which was the root cause of the segfault.

[FIX] #3886 Selected columns in category grid¶

The topic grid now correctly remembers and applies the columns that the user has chosen to show for each category, including custom fields. The CSV export also now respects the visible column selection rather than exporting a fixed hardcoded set of columns.

[FIX] #3887 Error opening project config¶

Fixed an error that prevented the project configuration panel from opening after the GraphQL layer was removed. The settings forms for general project config, branch prefixes, and project groups now correctly use the new REST endpoints.

[FIX] #3892 No categories in event rule editor¶

Fixed the category combobox in the event rule editor showing "No Data" instead of the list of available categories. The issue was caused by an incorrect MongoDB collection accessor introduced during the admin plugin migration.

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.