SignDoc Standard
This topic lists enhancements introduced to SignDoc Standard in this product release.
Token-based personal certificates
SignDoc Standard now supports token-based AATL certificates issued by GlobalSign when the SignDoc Device Connector is installed on the signer's local Windows desktop computer. The SafeNet eToken 5110 Series is supported.
Software-based databases that store users’ public/private key pair
Personal certificates installed in the Windows Certificate Store are displayed by SignDoc Standard when SignDoc Device Connector 3.2 is installed. The signer can select the appropriate certificate.
Enable use of signing method 'Personal certificate'
SignDoc Standard is extended with a new signing method. Use "Personal certificate’" to indicate a signature field as reserved for a digital certificate residing on the user’s computer. The package creator gives you the ability to select a handwritten signature, photo capture, click-to-sign, signature image, signature stamp, or the default appearance defined by SignDoc Device Connector 3.2.
Authorized download of completed documents
You can give signers and reviewers the option to download final documents from SignDoc Standard instead of sending them email attachments. Authentication is used to grant recipients access to the documents.
Signing packages with TSP signature signing method can be delegated
The ability to delegate a signing request to someone else to sign the documents is supported for recipients who need to sign via a trust service provider. The recipient provides the name and email address of the person to delegate the signing session to. The trust service provider remains the same.
Open documents on the first page
SignDoc Standard adds support to always display the first page of a document in the Signing Client, whether or not it contains a required field. The configuration setting client.signing.document.display.firstpage.enabled for the account is introduced. If set to "on," the first page of a document is always displayed when opened in the Signing Client. If set to "off," the page containing the first interactive field is displayed when a document is opened in the Signing Client.
Make the first signature method the default for the signer
The cirrus.package.enforceSigningMode.default setting defines whether the signer signs the rest of the signature fields with the same signing mode that was used to sign the first signature field. This setting can be overwritten by a signing package creator if the setting cirrus.package.enforceSigningMode.overwritable is enabled.
Update a signature field
The signing mode options of an already STARTED signature package can be updated if the provided signature field is unsigned, and the assigned signer has not signed any other assigned fields.
SigningEvent plugin extended
The SigningEvent plugin is extended with a new value to sign the audit trail of the final individual documents.
Endpoint to initiate creation of the final document
The new REST API call POST /rest/v8/packages/{packageid}/createFinalDocument gives developers the ability to handle use cases where the final container document needs to be initiated.
Account setting to predefine signature methods
The default, pre-selected signature methods to create a signature package are no longer fixed and can be defined for an account. The configuration is done using the new setting client.signing.signaturefield.signingmodes.default.