priint:suite - Patch 164 - Change Log
This patch, released on October 8, 2025, continues development on new features and includes several bug fixes.
The build name on FTP: 4.6.0.881
Software
Windows:
PubServer_Install_Update_4.6.0.881.zip
Linux:
PubServer_Update_4.6.0.881_UbuntuLinux.deb
Release Notes
The Admin application
| Issue Key | Summary | Release Notes |
|---|---|---|
| ADMIN-2674 | Apply the UI improvement for the process screen | The new shared UI improvements have been applied to the current process screen for consistency across applications. |
| ADMIN-2648 | Cannot remove value from the value list | Fixed an issue where the UI did not display any message when the backend returned an error during value deletion. The frontend now properly shows a toast notification if the value cannot be removed (for example, when it’s still in use), ensuring users are clearly informed of the failed action. |
| ADMIN-2634 | Content module - Reset does not reload initial content after no-results filter | In the Content module, after running an Advanced Search that returns “No data found.” clicking Reset now correctly reloads and displays the initial content view. |
| ADMIN-2629 | Content | Data Type isn't saved when Add/Edit a key Value | Resolved an issue in the Content module where the Data Type field was not being saved when adding or editing a key value. The Data Type is now stored correctly after each update. |
| ADMIN-2529 | Support get Object Storage and print BPM information | Displaying Object Storage type and version (e.g., MinIO) in the Technical Info section. The Pubserver now retrieves and exposes this information via API. |
| ADMIN-2520 | Check and fix the issue: the Set Publication Metadata script doesn't work completely for the case: update metadata values = false | Resolved an issue where the Set Publication Metadata script did not execute correctly when updating metadata values to false. The script now handles this case as expected. |
The planner application
| Issue key | Summary | Release notes |
|---|---|---|
| PRIINT-12221 | Download Document Template - improve file naming | Improved file naming when downloading a Document Template. |
| PRIINT-12220 | Publication List View - Filter "Document-Templates" only works for lower case Input | Publication List View - Filters: "Document-Templates", "Templates" and "Page-Templates" work independently of case. |
| PRIINT-12199 | Error in Process Modeler - inMapping in call activity | Fixed a bug where the embedded editor added an invalid $type attribute to <camunda:in> mappings, causing process deployment to fail. Deployment now works as expected. |
| PRIINT-12187 | Percentage sign in settings.update.ini needs to be masked | Passwords containing % can now be used by the updater. |
| PRIINT-12112 | Provide a Java API for Admin Panel to fetch rendering-service version and status information | A new PubServerAPI interface RenderingServiceStateServiceLocal has been added. To fetch the information currently available on rendering-service, its workers, and rendering-server instances those workers collaborate with, use this Java code snippet:PlannerEngineServiceLocator.INSTANCE.getRenderingServiceStateServiceLocal().listCurrentWorkers(); |
| PRIINT-12088 | Fetching Camunda version from priint-bpm for Admin Panel | A new endpoint was added to priint-bpm to enable fetching both priint-bpm and the embedded BPMS engine versions. This is used by an implementation of our new PubServerAPI interface PriintBpmStateServiceLocal.To fetch the versions in Java code:PlannerEngineServiceLocator.INSTANCE.getPriintBpmStateServiceLocal().getPriintBpmVersions();If an empty optional is fetched, no priint-bpm could be contacted (which is fine for some of our clients' deployments). |
| PRIINT-12087 | Fetching object storage type and version information for Admin Panel | There is now a way of obtaining Object Storage version information configured in the same place Object Storage access credentials are set for the PubServer. These version descriptors can be retrieved with PubServerAPI:PlannerEngineServiceLocator.INSTANCE.getObjectStorageStateServiceLocal().getObjectStorageState(); |