Skip to content

SEAL Operator 1.6.0


New Features

  • seal-logrotate to cleanup outdated log files is no longer included in the installation of SEAL Operator. Please download and install SEAL Logrotate separately, refer to SEAL Logrotate documentation. (SOP-484)

  • MongoDB 4.4.4 has reached the end of its lifecycle. Please update your MongoDB to version 7.0.0. As of SEAL Operator 1.5.1, a replica set has to be configured in MongoDB, refer to Configuring a Shared Replica Set and Initializing the Database in MongoDB documentation. (SOP-610)

  • Node.js has been updated to 20.12.2 due to security reasons (SOP-604, SOP-611, SOP-615)

  • The MongoDB Node.js driver has been updated to 6.3.0. (SOP-597)

  • SEAL Operator has been updated to Angular 17. (SOP-465)

  • ltiff2pdf 4.2.0 is contained in the delivery. (SOP-607)

  • Ghostscript has been updated to version 10.03.1.1. (SOP-625)

  • With the renaming of PLOSSYS 5 to PLOSSYS Output Engine, the respective operator panel has been renamed to Output Engine as well. (SOP-600)

  • SEAL Operator has a new application logo. (SOP-614)

  • node-p4rest service has been updated to version 6.4.6 containing the update of Node.js to version 20.12.2. (SOP-623)

  • To release and collect pickup jobs via the new PLOSSYS Mobile Client, two new REST routes have been added to the Operator API. (SOP-617, SOP-618)


Bug-Fixes

  • The note displayed when no panel is open has been improved. (SOP-587)

  • When calling SEAL Operator with a link to a panel the panel did not open even if it was selected in the sidebar. This bug has been fixed. (SOP-621)

  • A rare bug where login with Azure AD as ID provider did not work has been fixed. (SOP-622)


Known Issues

  • When uploading large files (>1 GB) the Web Portal could freeze. You might have to reload the web site and restart the upload.

  • The PLOSSYS 4 panel shows sometimes the wrong target printer. (SOP-40, SOP-202, SOP-214)

  • New login screen because of a session time-out isn't shown automatically but just after an action. (SOP-215)

  • In My Documents, if a directory has been created by a technical user for an owner, the owner can see the created directory but not the files within. (SOP-626)

  • If the owner is not the creator of a share, they do not get access notifications. (SOP-627)

  • The required fields are not checked anymore when clicking on Start printing. (SOP-629)


Back to top