SignDoc Standard

The "Initials" field type is newly added to the list of interactive field types. The new field is used to record the signer's initials. Initials are often formed from the first letters of a person's full name. Unlike signature fields, text fields, and check boxes, the Initials field can also be assigned to a recipient with a reviewer role.

For details, see Sign documents in the SignDoc Standard Help.

Copy and paste capabilities are supported for interactive fields. Once a field is defined, it is possible to place the field in the same size in another place of the document for the same signer. All interactive fields are supported. In addition to copying an interactive field to a single position in the document, a field can also be copied to the same page position across all pages of a document.

For details, see Prepare documents in the SignDoc Standard Help.

If uploaded documents contain unassigned fields and only one recipient exists who acts as a signer, it is possible to automatically assign the fields to the signer. The assignment must be confirmed by the creator of the signature package.

After starting a signing package, you can update the signing workflow for recipients who have not yet started the signing process. This feature is available for all signing workflow options. The update is documented in the audit trail. Only properties owned by the recipient can be updated. It is not possible to update package details, documents, or document fields.

For details, see Update recipients in a started signing package in the SignDoc Standard Help.

For "Complete one by one" and "Complete in customs order" signing workflows, you can change the order of the recipients.

For details, see Update recipients in a started signing package in the SignDoc Standard Help.

The manual email sending function of SignDoc Manage Client for a completed package is extended with an option to include a download link.

For details, see Download link in the SignDoc Standard Help.

The logo on the final signing package audit trail document is now customizable. The configuration can be done per tenant on the account level. If no logo is provided, the default Kofax logo is used instead. SignDoc supports several image types.

For details, see "Logo on the final audit trail document" setting in the SignDoc Administrator's Guide.

To make the signature color stand out from the text, it is now possible to specify the color for a handwritten signature per account. The new setting *.signing.render.color.handwritten is introduced for the SignDoc signing handler.

For details, see Styling the signature capture dialog box in the SignDoc Browser Capture Help.

SignDoc 3.3 introduces the use of webhooks for implementing extensions to communicate with the SignDoc server. The webhook concept replaces the previous server-side plug-in interfaces. With this release, webhooks for the state change and TSP events are available.

For details, see "Webhooks" in the SignDoc Standard Developer's Guide.

A completely redesigned SignDoc Authentication Module (SAM) is included in this release. A one-time installed SignDoc Authentication Module (SAM) for Single Sign-On can be connected with multiple SignDoc servers at the same time. The configuration of SAM is done once in the application.yaml file, and the tenant-specific SAML2 configuration is done in SignDoc Standard by the account administrators. The new SAM supports load balancing and individual encryption per server.

For details, see "SignDoc Authentication Module (SAM)" in the SignDoc Standard Installation Guide.

If packages should only remain in the SignDoc database for a certain time, the new settings cirrus.package.retention.enabled, *.states, *.olderthan, and *.beforethan can be used to define the behavior. The decision to purge signing packages depends on the creation date and state of a signing package. The settings require system administration rights.

For more information, see "Documents and packages" in the SignDoc Standard Administrator's Guide.

New team members will receive a notification containing a link to accept the invitation to join the team. Until the invitation is accepted, the user is managed with the status of "Invited" and cannot access the signing packages of the team and vice versa. A team manager can re-send the invitation to join a team.

Users can now remove themselves from a team. The team manager is notified by email.

Instead of renewing the MAX_SIGNATURE_PACKAGES and MAX_USERS license parameters for term licenses on January 1 of each year, SignDoc now performs the renewal on the expiration date (month and day).