7.16.3

Clarive 7.16.3 Release Notes¶

Release date: March 14, 2026

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

Improvements and issues resolved¶

[ENH] #2315 Add username to Git commits¶

Commit and revision views now show both the Git author and the Clarive user who performed the push. This improves traceability when repository activity is triggered from Clarive and makes it easier to audit who actually launched each update.

[ENH] #2348 Show topic unread status for other users¶

Topic views now include a "Seen by" indicator so teams can quickly identify which users have already opened a topic. This reduces uncertainty during collaborative reviews and follow-up work.

[ENH] #2683 Back to origin workflow transition¶

Workflows now support returning a topic only to the original status it came from. This gives workflow designers tighter control over rollback or rework paths and avoids transitions to unintended intermediate states.

[ENH] #3313 Topic Activity: Improve format when modifying fields¶

Topic activity entries have been redesigned to be easier to read, especially for field changes. The update improves formatting for text diffs, files, users, CIs, releases and other field types, making audit trails clearer and more useful.

[ENH] #3422 Kill rule when WS pipe closes¶

Web service rules executed through ws_pipe now stop automatically when the client disconnects. This prevents unnecessary background processing and improves cleanup of abandoned executions.

[ENH] #3558 Denied actions in roles¶

Role configuration now supports explicit denied actions in addition to allowed ones. This makes permission definitions more precise and gives administrators a clearer way to block selected operations even when broader access exists elsewhere.

[ENH] #3560 Rule specific actions¶

Permissions can now be assigned to specific rule actions instead of only broader rule bounds. This gives more granular control over what users can do with rules and improves the administration experience in the role editor.

[ENH] #3677 UserGroup administration revamp¶

The UserGroup administration screens have been refreshed to improve editing and navigation. The update includes better scope handling and a more practical editing workflow for complex permission setups.

[ENH] #3680 Role editor multiselect scopes¶

The role editor now supports selecting multiple scopes for action permissions. This makes it easier to define access rules that apply to more than one scope without repeating the same configuration.

[ENH] #3684 Defaults to mongoc driver¶

Clarive now defaults to the mongoc driver. This aligns the default database driver with the current supported stack and reduces the need for additional configuration in new or upgraded environments.

A new "Jobs" entry has been added to the main menu, making job monitoring and related views easier to reach from the main navigation.

[ENH] #3689 Git personal access tokens¶

Users can now create Personal Access Tokens (PAT) for Git authentication over HTTP without exposing their normal password. This improves security for integrations and makes it easier to connect Clarive repositories to external Git tools and automation.

[ENH] #3692 Add CI fields filters to topic category grids¶

Advanced filters in topic grids now support CI fields directly. This makes it easier to narrow down topics using values from related resources without relying on custom workarounds.

[ENH] #3695 Show releases in job report panel¶

Job report panels now include releases in a clearer contents layout. This gives users a better overview of the deployment information associated with each job and improves navigation in long reports.

[ENH] #3708 Clarive trash for deleted topics, cis and rules¶

Clarive now includes a Trash area for soft-deleted topics, resources and rules. Deleted items can be searched, reviewed and restored, with validation for dependency order and conflict situations. This provides a much safer recovery path when something is deleted by mistake.

[FIX] #209 "tail: no files remaining" message when stream is finished¶

Removed a misleading tail: no files remaining message that could appear when a streamed job log finished. Job output is now cleaner and avoids confusing users with a harmless internal message.

[FIX] #2536 Deploy button spins when changing status from topic grid¶

Fixed the topic grid so only the button that was actually clicked shows a loading state during a deploy-related action. This avoids the impression that multiple actions are running at the same time.

[FIX] #3164 Revision link loses browser history¶

Corrected revision links so browser navigation works properly after opening a revision view. Users can now move back through the interface as expected.

The Project Settings menu is now hidden when a user has no effective access to it, while root users still keep visibility as expected. This removes confusing navigation options and aligns the UI with actual permissions.

Context menu entries that open views in a new tab now behave as proper links. This improves navigation consistency and fixes browser interactions such as opening in another tab.

[FIX] #3430 Wrong sorting in topics grid when opened from other topic¶

Fixed topic-grid sorting when a grid is opened from another topic. Rows now keep the expected title ordering instead of showing inconsistent sort results.

[FIX] #3652 Do not evaluate closed statuses in SLA¶

SLA processing now skips topics that are already in closed statuses. This avoids unnecessary evaluations and prevents incorrect SLA transitions on items that should no longer be processed.

[FIX] #3655 Event daemon not responding¶

Resolved an issue in the event daemon that could block or destabilize processing in some situations. Event handling is now more reliable under debug and runtime conditions.

[FIX] #3668 The resize of the Ace Editor does not work properly when called from all the operations that can invoke it.¶

Ace Editor resizing has been corrected across the different views and operations that use it. Editors now adapt more reliably when windows are resized, maximized or reopened.

[FIX] #3676 Aditional data of changesets in job monitor error on click¶

Fixed an error that could occur when clicking the clip icon to open additional changeset data in the job monitor. The details panel now opens correctly.

[FIX] #3678 Personal reports revamp¶

Improved the stability and behavior of personal reports. This includes better handling of selected fields and a more consistent editing experience in the report designer.

[FIX] #3690 Reports bugfixes¶

Report filters and exports have been corrected in several areas, including date filters, dynamic operators, field rendering and CSV output. These fixes make report results more accurate and reduce inconsistencies between the grid and exported data.

[FIX] #3696 Job end event failure caused by DemolishAll loading¶

Fixed a failure during job end event processing caused by an unnecessary DemolishAll module load. This prevents avoidable post-job errors and makes job finalization more reliable.

[FIX] #3698 Reports bugfixes II¶

Report generation now handles sibling and child category fields more consistently. This fixes missing or incomplete field visibility in complex report definitions.

[FIX] #3699 User admin users can always change internal user password¶

User administrators can now reliably change passwords for internal users when their permissions allow it. This restores the expected administration behavior.

[FIX] #3700 IF var condition editor restoring wrong values¶

Corrected the IF var condition editor so saved values are restored properly when the condition is edited again. This includes the numeric option and the condition state, preventing forms from re-opening with misleading values.

[FIX] #3701 CI versions don't store the user that performed the update¶

CI version records now store the user who actually performed the update. This improves traceability in version history and makes audit information more complete.

[FIX] #3705 Slack push messages should navigate to branch¶

Slack push notifications now generate the correct repository branch links. Users can open the referenced branch directly from the notification instead of landing on an incorrect page.

[FIX] #3707 Events being purged too early¶

The default event purge period has been corrected so event data is retained for the expected amount of time. This avoids premature deletion in default configurations.

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.