Skip to main content
Skip table of contents

Release information

Release dates

| Major release 2025.1.1 |


Highlights CORE


Upgrade to Jetty 12 | Breaking change

We have migrated the Censhare Server from Jetty 9.4.56 to Jetty 12.0.17, aligning with the latest Jakarta EE 10 standards, the official successor to Java EE. This is a breaking change and requires some action from anyone syncing with the master branch or working with the version 2025.1.

Upgrade to Java 21

The core Censhare Stack, incl. Server, Cloud Gateway, and Static Resource Server, is now using the latest Java version. This ensures robustness against any possible security issues, a long-term support, as well as a better code based on new methods and classes.

Upgrade to PostgreSQL 17

To enable a better data management and a more secure database system for our customers, we fixed any breaking changes required to upgrade to the latest PostgreSQL version and conducted an extensive testing to ensure the compatibility. We now officially recommend PostgreSQL 17 for Censhare installations.

New design for Censhare Web

Censhare Web Client has undergone a few changes that, without affecting the functional aspects of the application, drastically enhance the overall user experience: the elements that are important for fulfilling the current task, are better highlighted. This and other changes, such as more clear active state for tabs and more prominent actions on the upper navigation pane, provide visual guidelines through the everyday complexity.

Web Client disconnection issues solved through keeping the WebSocket alive

Web Client used to have some connection issues when default load balancer, proxy, or other forefront appliances' settings assumed a keep-alive functionality on its side. Instead of relying on configuration only, we decided to implement such functionality as an additional component inside the Censhare Web Client. It sends periodical ping requests via WebSocket, to prevent closing the connection prematurely.

Web Client usage tracking with matomo

Starting from this release, we will track user interactions with the Web Client UI using matomo. The goal is to identify the UI components that are mostly in use and focus on what can truly enhance user experience. No personal data will be collected. The tracking should help us in data-driven evaluation of customer feature requests.

Java Client returns to foreground after successful login

Before this enhancement, users had to bring the Java Client back to foreground manually, even after a successful Keycloak login. Now, the user is automatically taken back to the Java Client for continuing their work. This saves a few clicks and eliminates any possible confusion around whether the login was successful.

Drag area on widget is retained even if the widget title is hidden

Previously, widgets could only be repositioned by dragging their title area. However, if widget title was hidden by configuration, users lost the ability to move widgets. Now, a thin area is preserved where the title used to be, to enable users to drag-and-drop widgets.

Read more

Manage widgets


Highlights DAM


@mentions: tagging users in communication on the asset

Collaboration is king. That’s why we continuously improve functionality of the Communication tab.

This time, we added a possibility to at-mention users in messages and tasks by typing “@” and then the name of the user or a user group (autocomplete provided). Notifications will appear in the Web Client notification center for the tagged users.

Setting marker on a zoomed image | UX improvements

It used to be a bit of a challenge before: setting a marker on a proper position after zooming in or out of the asset preview. Now, the behaviour is stable: the marker is set in the area still visible in the Annotations widget. I.e., the level of the zoom won‘t be reseted, and users are able to place markers exactly where they are intended to do so.


Highlights Print Management


Censhare Web: Export PDF of the issue in FlatPlan

Censhare Web users that work with FlatPlan can now generate a comprehensive preview of an issue. Such preview is a “snapshot” of major configurations applied in the FlatPlan Editor. The result can be saved in PDF format or printed directly for sharing purposes.


Highlights Media Asset Management

Decomposition of bundled assets

This feature is targeted at those who work with 3D models, video and other project archives.

Previously, users had to extract files from ZIP archives locally, upload them to Censhare, and re-create their relationships manually. Now users can upload the entire archive and it will be decomposed within the system. The folder structure will be kept, each file inside the archive will become the master file of its own asset, and the ZIP archive will become the parent asset of all others.

The entire process is transparent and easy manageable for the user by means of an intuitive UI implementation.

Screenshots for 3D model assets

It is now possible to capture the current view of a 3D model asset and use it independently as an image asset. The screenshots can be done with just one click and in a high resolution if necessary. The resulting assets are linked to the original 3D model asset through a relationship and can be quickly found on its page.

Timecode support for video assets

Timecode support allows referencing video frames on video assets instead of simple timestamps. It has been implemented for each affected tab on the asset page: the Preview, the Editor, on markers, and on the Analysis tab. The new feature enables users to trim videos more precisely, to create more accurate markers, and to better align transcriptions with visuals.


Complete list of release changes

2025-1-Release-notes.xlsx


Known issues

The full list of known issues present in this and earlier Censhare versions can be found on this page.

Discrepancy between video length in different widgets

When you upload a video to the Censhare system, a few storage items are created from the original one. They are used in different widgets. For now, the displayed number of frames is rounded down for the master file used in the Editor, without the actual asset length being cut. Consequently, in the Editor, the video appears as one frame shorter than in the Preview and Annotation widgets (Overview and Communication tabs respectively).

We are working on solving this issue in the nearest future.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.