priint:suite - Patch 1 - Change Log
This patch, released on August 5th, 2026, delivers a set of targeted fixes and usability improvements identified after the official 4.8 launch.
The build name on FTP: 4.8.0.715
Windows:
PubServer_Install_Update_4.8.0.715.zip
Linux:
PubServer_Update_4.8.0.715_UbuntuLinux.deb
Release Notes
The admin application
| Ticket | Summary | Release Note |
|---|---|---|
| ADMIN-4003 | Sort column in Metadata table sorts alphabetically, not by number | Fixed an issue where the Sort column in the Metadata table sorted numbers as text. Result: sorting now follows the correct numeric order. |
| ADMIN-3947 | Content values not updated when working with dynamic context | Fixed an issue where editing fields in the dynamic context (Well, Assortment, Language, Country) did not update their values, they kept showing the old value, this only happens in "aiomua" database. Result: dynamic context fields now update correctly. |
| ADMIN-3956 | User re-import hangs when restoring deleted users | Fixed an issue where importing an exported user list would run indefinitely and never complete, preventing deleted users from being restored. Result: user import now completes successfully and shows the correct status message. |
| ADMIN-3948 | Application error when opening the Text tab / Key Values tab | Fixed an intermittent issue where opening the Text tab or Key Values tab sometimes triggered an application error. Result: the tab now opens and shows its content reliably. |
| ADMIN-4009 | Import Dialog footer buttons have no spacing | Fixed a spacing issue between the action buttons in the Import dialog footer. Result: buttons now display with proper spacing. |
| ADMIN-3936 | Add New Domain Path property | Added a new domain path property that the deployment process picks up automatically from the installer. Result: users no longer need to enter the domain path manually during deployment. |
The priint:planner application
| Key | Summary | Release Notes |
|---|---|---|
PRIINT-12840 | pubserver::plannerengine::ImageUtilsServiceBean.getPreviewOfMediaAsset Bug | Fixed an unhandled case in ImageUtilsServiceBean.getPreviewOfMediaAsset() so that it now returns null instead of throwing an exception when the image file does not exist. |
PRIINT-12834 | Planning cannot be removed as long as text entity is selected | Fixed an issue in the PublishingHubDB Connector where planning could not be removed while a text entity was selected, causing an exception to be logged. |
PRIINT-12820 | Neowise - Bulk Edit - Editing stage on different types of documents erases plannings | Editing stage on different types of documents erased plannings. Solved |
PRIINT-12807 | Licenses for 4.8 | Licensing info has been updated |
PRIINT-12770 | Neowise - Notes popup is displayed outside viewport when opening a note near the bottom of the page | Note pop-up was sometimes displayed outside of viewport. Fixed |
PRIINT-12757 | Migration Documentation - 4.8 | Migration documentation was prepared. |
PRIINT-12755 | Locked document in the multe edit mode | Documents were not locked when opened in multiedit mode. Fixed |
PRIINT-12745 | Notification if a process instance is deleted. | Users are now notified with a general message when a process instance they created is deleted. |
PRIINT-12684 | Allow custom applications in the SSO post-login screen and app switchers | Added support for displaying custom applications on the SSO post-login screen and in app switchers. |
PRIINT-12681 | Suffix SSO cookie with referrerPort to isolate InDesign SSO sessions from web app sessions | Signing in to the priint:comet InDesign plug-in through single sign-on no longer affects a web application (such as the planner or admin app) that is already signed in in the same browser. The plug-in and the web application now keep independent sign-on sessions, so you can stay signed in to both at the same time, and signing out of one does not sign you out of the other. |
PRIINT-12626 | Document locks behave unexpectedly after signing in to InDesign via SSO | Document locks created from workflow, background job and REST contexts are no longer displayed as "InDesign Desktop" in the lock overview; they are now attributed correctly. Locks from an InDesign client that signed in via SSO are classified as InDesign Desktop. The InDesign SSO login flow no longer sets unused browser cookies. Existing locks keep their original classification; the change applies to newly created locks. |