SignDoc Standard

This topic describes changes in the SignDoc Standard behavior since the previous release.

Deprecated features

The SignDoc plugin interface for customer extensions is deprecated and replaced with the webhook concept.

Using H2 database with file-based storage for non-production purposes

SignDoc Standard 3.3 upgrades the H2 in-memory database for non-production purposes to version 2.1.214. The new version of H2 introduces schema changes that are not compatible with its earlier versions and therefore cannot be reused with the existing SignDoc H2 database. So users must delete the old H2 database before upgrading to 3.3. The content of the previous file-based storage is no longer available after the upgrade.

Users must actively agree to join a team

SignDoc users can no longer join a team unless they actively agree to do so.

Settings category 'Documents and packages' is divided

The Documents and packages category of the administration settings is divided into Document and Package sections. The Document section contains the settings related to documents, while Package contains the settings related to signing packages.

Pulsing action icon for TSP signing

The Signing Client displays a pulsing action icon (open-in-new icon) in the Review and Sign view indicating a redirect to another provider.

No Docker file for Windows Server 2022

To build a SignDoc Standard image under Windows Server 2022, you need to copy file Dockerfile.Windows.2022 to file Dockerfile.Windows and build images with build_images.cmd. Only 01_base_image and 04_env_variables samples are supported on Windows Server 2022. For more information, see the readme.html file in the docker directory of the SignDoc Standard package.

No mssql-server-windows-express Docker images for Windows

The official mssql-server-windows-express Docker images for Windows are removed from the Docker repository. As a result, the Docker samples for Windows are no longer supported.