SignDoc Standard

SignDoc Standard is updated to use Spring Boot, introducing a new directory structure that simplifies navigation with clear and logical folders for the Java Runtime Environment, shared libraries, extension modules, database initialization scripts, and resources. Essential settings such as the database connection and external host URL configurations require application at startup and can be configured in the SignDocStandard.yml file.

The update also includes additional files for setting up and managing the SignDoc Standard service on Windows, including configuration, logging, and service management samples, as well as examples for Docker Linux and Windows containers, and a default Logback logging configuration.

For details, refer to the SignDoc Standard Installation Guide.

SignDoc 3.4.0 introduces support for Microsoft and Google as OAuth authentication providers for external authentication of recipients. Signing package creators can include one or more authentication providers for recipients when assembling the signing package, providing flexibility in managing access controls.

The Single Sign-On (SSO) authentication module is fully integrated into SignDoc 3.4.0. Originally released as a separate module requiring manual installation and configuration, the SSO module is newly streamlined as an integral part of the SignDoc platform. Existing SignDoc SSO settings and configurations are unaffected by this integration, ensuring seamless continuity for users who have already set up their SSO authentication.

Connect SignDoc to a third-party Large Language Model (LLM) to leverage generative AI capabilities. SignDoc enhances the creation of the document description experience through AI-driven assistance. SignDoc uses generative AI to identify the main language of the given text and to provide a concise, generic summary of that text written in the specified language.

The SignDoc AI integration settings include URL endpoints and methods for authentication supporting the Azure OpenAI and OpenAI providers. Account administrators can deploy the settings.

For details, refer to the SignDoc Standard Administrator's Guide.

This release introduces persistent filtering of signing or template packages. If a user leaves the list and returns to it later, the most recent filter settings are retained so that users can quickly pick up where they left off and continue examining the filtered results. The filter settings are unique to the browser, and they are preserved even when the user leaves the SignDoc Manage Client.

Administrators can configure several new settings to enhance the appearance of masked fields. The options include customizing the color of the masking box, as well as the color and text displayed on masked fields. Additionally, administrators can specify the font used for the displayed text, to improve the user experience.

For in-person signing, you can configure separate end URLs that are triggered when the signing host or the signer ends the session. Additionally, you can set up an Expired Session URL for in-person signing sessions. Both URLs support placeholders for account ID, package ID, and signer IDs, which are automatically replaced with data.

If a page expires during a remote signing session, the process for resuming the session is now simplified. This enhancement eliminates the need to return to the email inbox.

For signing package recipients in the Start state, you can update the phone number for sending the access code.

SecureID provides a robust way to associate signers with their signed documents in a signing package, ensuring the integrity of digital transactions. This unique identifier is generated using, but not limited to, information about the signer, including the signer's name and the displayed timestamp. SecureID is displayed in the signature appearance and the audit trail when signing with a personal certificate.

Use the following setting to customize the text to reflect your brand name or service:

cirrus.document.signing.c2s.logo.text.

Use the following configurations to adjust the read timeout for TSP of 300 seconds:

• webhook.type.tsp.timeout.read
• webhook.type.tsp.timeout.write
• webhook.type.tsp.timeout.connect

This version introduces an endpoint http://<server>/cirrus/test/cookie that allows you to verify whether the infrastructure or environment where SignDoc is installed supports cookies as needed by SignDoc, for example for Single Sign-On (SSO).

Tungsten SignDoc supports activation codes for the Tungsten Automation license server through the Tungsten TotalAgility License Web API. Administrators can set up the license configuration.