1.11 release notes

Before attempting to upgrade to Document Engine 1.11, first upgrade to Document Engine 1.10 if you haven’t already, and make sure your application still runs as expected.

We always verify that the release process is seamless when upgrading to the newest version from the last minor release. If you’re using an older version, make sure to upgrade one minor version at a time.

Example: If the latest version is 1.6.1 and you’re running 1.3.x, upgrade to 1.4.x first, then to 1.5.x, and only then to 1.6.1.

Refer to our upgrade guide for more information.

Highlights

Digital signatures

This version adds a new signingCertificateChain field to the schema of the signatures returned by Document Engine when a client requests signatures in a document.

Affected endpoints

All endpoints that work with build instructions are affected by this change, including:

  • GET /api/documents/{documentId}/signatures
  • GET /api/documents/{documentId}/layers/{layerName}/signatures

Refer to Document Engine’s API reference for more information.

Web SDK processing operations

This version adds support for additional document processing operations when invoking processing via Instance#applyOperations from Nutrient Web SDK:

  • addPageMargins to add insets and outsets to pages.
  • updateMetadata to update document metadata.

GdPicture update

This version ships with GdPicture 14.3.12.

Performance improvements

This release improves the performance of filesystem operations, fixing a performance regression that was introduced in 1.8.0.

Breaking changes

Database connections

We found that versions 1.10.0 and 1.10.1 stopped handling the DATABASE_CONNECTIONS environment variable correctly, and it defaulted to 10 instead of 20. To address this, we recommended setting the PGPOOL_SIZE variable instead of DATABASE_CONNECTIONS. However, as of this version, this is no longer a valid recommendation, as the issue was fixed, so be sure to revert back to the DATABASE_CONNECTIONS environment variable.

Database migrations

This release doesn’t include any database migration.

Changelog

A full list of changes, along with the issue numbers, is available here.