OptimiDoc Server Help Center
OptimiDoc Server Help Center
Breadcrumbs

Release Notes

This section contains version history and change logs for OptimiDoc Server releases. Each release note documents new features, improvements, bug fixes and any breaking changes that administrators should be aware of before upgrading.

Every entry includes the version number and release date, new features, improvements, bug fixes where relevant, any breaking changes that require administrator action, and upgrade notes.

Version 26.07 — July 2026

Released 7 July 2026. Version 26.07 is the first published release since 26.01 (January 2026) and consolidates roughly half a year of development. Its headline change is the roll-out of the React administration UI as the default interface, alongside major additions to printing, quotas, security and scanning. Because it spans several interim development cycles (26.02–26.06 were not published as separate releases), administrators upgrading from 26.01 should read the upgrade notes below carefully.

New Features

  • React administration UI as the default interface. The server's root address now opens the modern React UI. Sign-in gains Remember me with a flash-free redirect for already-authenticated users, login/logout and session-extension synchronised across browser tabs, role-based default dashboard layouts, and a theme system (light, dark and branded themes) with a dark-mode-capable login page. The classic MVC interface remains available at /old.

  • Named IPP queue connectors. Driverless printing can now be organised into named IPP queue connectors, each with its own set of print attributes, so different user populations can be given different driverless printers.

  • Node-side IPP servers with pull-based configuration distribution. Print nodes (OPN) can host their own IPP servers, and IPP queue configuration is distributed across the cluster and print nodes on a pull basis, keeping every node in step without manual copying.

  • Quota enforcement with settlement. The quota system enforces print and copy limits using a dedicated quota database and a settlement step that reconciles reserved against actual cost.

  • Scan workflow editor overhaul. The scan-flow editor was substantially reworked: workflow import and export (including bulk drag-and-drop import), a full secondary-destinations model with Always / Only-on-errors delivery, drag-to-reorder parameters, OAuth (Microsoft/Google) e-mail input sources, and editor features gated by licence capabilities.

  • PDF job analysis. A new analyzer inspects PDF print jobs (page counts, colour and other attributes) using Aspose.PDF to improve accounting accuracy.

Security

  • AES-GCM encryption with key migration. Small-value and file encryption moved to AES-GCM, with credential and destination encryption centralised in the database layer and an administrator action to migrate legacy-encrypted data to the new scheme.

  • Sensitive values such as PINs and passwords are masked or removed from logs, and cryptographically secure random generation is used for generated PINs.

Improvements

  • Performance for large deployments. User, device, department and billing-code pickers were converted to asynchronous search rather than loading every record, and report and job exports now stream instead of buffering large result sets, so the UI stays responsive on estates with thousands of users and hundreds of devices.

  • SNMP-driven device onboarding. New devices start with the default SNMP configuration preselected, and model and serial number can be auto-detected over SNMP. Vendor-specific hints were added to device configuration labels, and duplicate IP addresses now produce a clear, localised error.

  • Terminology alignment: the English UI now uses Billing Code where it previously said Project.

Breaking Changes and Upgrade Notes

  • Default interface changed. After upgrading, the root URL redirects to the React UI (/ui). Bookmarks to the legacy UI should be updated, or reach it via /old.

  • .NET Framework 4.8 required. The web application targets .NET Framework 4.8; ensure the runtime is present on the server (see System Requirements).

  • Separate quota database. Enabling quotas uses a dedicated quota database in addition to the main OptimiDoc database.

  • After upgrading, use the encryption migration action (under Diagnostics → Encryption) to re-encrypt legacy secrets with AES-GCM.

  • For general upgrade guidance, see Upgrade and Migration.

Earlier Releases

Release notes for versions prior to 26.07 are maintained in the internal change log. For migration guidance between older versions, see Upgrade and Migration.