SigningHub Release Notes

October 2023

New Features

• Advanced Reporting (SHE-36080)

• SigningHub can now be integrated with Microsoft Power BI, this enables Enterprises to gain greater insights into user behaviour, document interactions, and view advanced reports, based on enterprise data. Advanced Reports enables the building of custom reports for Enterprises. The Power BI integration is limited to the Azure-hosted Power BI service and the on-premise Power BI product is not yet supported.

• Document Commenting (SHE-38877)

• SigningHub now enables document owners and recipient(s) to collaborate on documents and workflows by enabling them to post public, and private document comments. Users can place comments anywhere within documents and @tag individuals or comment for all workflow participants.

• Levels of Assurance Signature Limits Based (SHE-35951)

• SigningHub now provides an option within the service plan to define signature limits for each level of assurance, this enables Trust Service Providers and Enterprises to define limits for different types of signatures offered by SigningHub.

Improvements in this Release

• Binding Signature Logo to a Signing Server (SHE-34372)

• SigningHub now allows you to configure a signature logo against each signing server, in a role.

• Role-based Signature Appearance Configuration (SHE-36964)

• Administrators can now choose which signature appearance designs they would like to allow, for users, in a role.

• Service Plan-based Signature Appearance Configuration (SHE-36965)

• Administrators can now choose which signature appearance designs they would like to allow, for users, in a service plan. Administrators can configure a signature appearance and a signature logo for each signing server, in the service plan.

• Webhooks Configuration (SHE-35243)

• SigningHub now enables you to choose the events for which the document processing report (XML) will be sent to the callback URL, and the ability to toggle off the document processing report (XML) for each workflow.

• OTP/TOTP Authentication for Signature and In-Person Signature Fields (SHE-37790, SHE-37456)

• SigningHub now allows the document owner to configure One-Time Password (OTP), and Time-based One-Time Password (TOTP) authentication, for signature and in-person signature fields.

• Attachment Fields in a Workflow (SHE-36298)

• SigningHub now enables the document owner to add attachment fields in a workflow. Attachment fields are assigned to recipients, and the document owner has the option to make the attachments compulsory, for the recipient(s). Multiple attachment fields can be assigned to a recipient.

• Custom Signing Reason (SHE-36269)

• Administrators can now set predefined signing reasons together with a custom signing reason for a SigningHub role.

• Document Format Recording in Workflow Evidence Report (SHE-37904)

• The SigningHub workflow evidence report now records the original format of a document as it is uploaded to SigningHub, and that the document is converted to PDF.

• Document Listing Improvement (SHE-38876)

• The SigningHub document listing module now includes:
• Title
• Owner
• Date Created
• Last Modified 
• Workflow Type
• Status
• Location

Users can now order each column in ascending or descending order.

• Enterprise Support Email Address (SHE-22792)

• SigningHub now allows users to add a support email address, on an enterprise level. When configured, this email address is used for an enterprise's notifications, alerts, and support queries.

• QR Code in an Individual Workflow Type (SHE-35738)

• QR codes can now be added to a document, in the individual workflow type.

• CSC Signing Improvement (SHE-38650)

• CSC signing has been improved to use the verification profile, configured in the service plan, to retrieve revocation information at the time of signing, and to verify the document signatures.

• Redirection to the SigningHub Mobile App (SHE-17818)

• Users are now redirected to the SigningHub mobile app when they select a document workflow link from a SigningHub email. If the SigningHub mobile app is not installed, users are redirected to the Play Store/App Store to install the app.

• Role-based Cloud Drive Configuration (SHE-34219)

• SigningHub now allows you to configure, which cloud drives are available to users at the role level.

• Twilio SMS Connector Updates (SHE-38411)

• SigningHub now requires its users to configure an alphanumeric sender ID within the Twilio connector; for sending an SMS message to a United Kingdom (UK) mobile number.

• Performance & Security Improvements

• This release brings several performance and security improvements to different areas of SigningHub including Admin, Web, and API.
• Several third-party libraries have been updated to the latest version.

• Managing SigningHub Web Settings via REST APIs (SHE-37262, SHE-38293, SHE-38294, SHE-38295, SHE-38296, SHE-38298, SHE-38299, SHE-38300, SHE-38301, SHE-38302, SHE-38303, SHE-38304, SHE-38305, SHE-38307, SHE-38315, SHE-38316, SHE-38332, SHE-38538, SHE-38539)

• SigningHub REST APIs now allow the users to manage:
• Personal
• Profile
• Contacts
• Groups
• Cloud Drives
• Delegate Settings
• Signatures
• Library
• Notification
• Enterprise
• Profile
• Contacts
• Groups
• Users
• Roles
• Documents
• Library
• Notification
• Electronic Seals
• Reports
• Integrations
• Branding
• Logs
• Advanced Settings
• The "Get Packages" API has been updated and now has improved document status reporting capability.

Deprecated Features and Important Changes

1. In order to send an SMS message to a United Kingdom (UK) mobile number, the user will have to configure an alphanumeric sender ID within the Twilio connector.
2. This version will be the last version to support v3 API, it will deprecate from the next version.
3. To make attachments compulsory, the configurations have been shifted from permission level to field level.
4. The verification profile, configured in the service plan, will be used to fetch the revocation information at the time of signing and to verify the document signatures.
5. From 8.6 onwards, in case you are using the latest API Server with an older version of the SigningHub App:

• The user will not be able to sign a signature/in-person signature field for which OTP/TOTP authentication has been configured.
• The user will not be able to sign a document in which a compulsory attachment field has been assigned to the user.
• The user will be able to use the cloud drives even if the cloud drives are not allowed in the user role’s sub-settings.

Tested Operating Systems

Tested Database Server

Supported Upgrades

Ascertia SigningHub 8.6 supports the following upgrade paths:

* SigningHub Upgrade guide - 7.7.x to 8.x.x, this document can be found on the Ascertia Community portal in the documentation section for SigningHub or in the docs folder of the SigningHub 8.5 product release. If you require further assistance with upgrading SigningHub, please contact Ascertia customer support.

Supported ADSS Server

Compatibility with Earlier Versions of SigningHub

SigningHub (iOS) & (Android) 8.6 are compatible with the 8.5 version of SigningHub except for the features that are mentioned in the Deprecated Features and Important Changes section above.

For further details contact us at sales@ascertia.com or visit www.ascertia.com