26.2.0 Release Notes

Release date: 27th May 2026


Highlights


  • 🗓️ Preservation actions can now be scheduled to run automatically on a recurring basis

  • 🧭 Menus, actions, and labels across Vault Admin are now aligned with the OAIS reference model (Ingest, Preservation, Access, Administration, Storage)

  • 🔗 Notifications can now be delivered via webhook with custom headers and a customisable message body, in addition to email

  • 📄 Docbyte Vault now ships with UBL 2.1 schemas so Peppol e-invoices can be archived and searched on their structured metadata

  • ✍️ Documents signed in Adobe Acrobat Sign are now ingested into the archive automatically

  • 🛠️ Several fixes around retention actions, legal holds, and deletion list visibility


New


🗓️ Scheduled Preservation Jobs

Preservation actions can now run automatically on a recurring schedule, alongside the existing manual run option. Administrators configure when an action should run and on which packages, and the system executes it at the scheduled time.


🧭 OAIS-aligned Naming across Vault

Menus, actions, and labels in Vault Admin have been renamed to follow the OAIS reference model, organising the product around Ingest, Preservation, Access, Administration, and Storage. Familiar terms have been updated for consistency, for example Plugins are now Preservation Actions, Run Bulk Plugin is now Execute Preservation Action, and Browse is now Fileplan.


🔗 Webhook Notification Sender

Notifications can now be delivered to a webhook in addition to email. Administrators configure a target URL, custom headers (for example an authentication token), and a customisable message body, and Vault posts the event to the configured URL when it fires.


📄 Peppol Invoice Schema Support

Docbyte Vault now ships with the UBL 2.1 schemas required to parse Peppol e-invoices and credit notes. Once ingested, invoice metadata becomes part of the indexed metadata and is searchable like any other archived document.


✍️ Adobe Acrobat Sign Integration

Documents signed in Adobe Acrobat Sign can now be ingested into the archive automatically. Once an agreement is signed, Acrobat Sign notifies Vault, which retrieves the signed PDF and its agreement metadata and ingests it as a new package.


📥 S3 Drop-Bucket Ingest Service

A new service enables ingesting files automatically as soon as they're dropped into a configured S3 bucket.


Improvements


🧾 Selectable AIP Metadata in Deletion Lists

For the Delete Content (Keep Metadata) post-retention action, administrators can now select which specific document metadata fields to keep per retention rule, instead of always keeping every field. The selected fields appear in the deletion list overview and the CSV export.


🔤 Strict Package ID Validation on Ingest

Ingest requests with special characters in the package ID now return a clear error instead of being silently modified. A per-environment whitelist can be configured for customers who need specific characters.


Bug Fixes


🔓 Unhold button and icon visibility

Resolved an issue where the Unhold action was not visible on packages under legal hold for some of the packages.


📥 Large base64-encoded ingest requests

Resolved an issue where ingest requests with large files sent as a base64-encoded string in the JSON body failed with a 400 error. The size limit is now configurable (default remains 20 MB) and exceeded requests return a clear error message.


👤 Duplicate username error surfaced

Fixed an issue in Vault Explorer where creating a user with a duplicate username failed silently. The UI now surfaces the validation error correctly.


🔁 Autocomplete dependent field refresh

Fixed an issue in Vault Review task forms where an autocomplete field could keep a stale value after the field it depends on was changed.