December 2022


New Features

  • Levels of Assurance for In-Person Signatures (SHE-34096)
    • SigningHub now supports defining a level of assurance for In-Person signatures. In-Person signers will be able to sign documents with certificates that comply with the Level of Assurance as defined by the Document Owner. Supported In-Person levels of assurance include “Simple Electronic Signature” (SES), “Electronic Seal” (eSeal), “Advanced Electronic Seal” (AdESeal) and “Qualified Electronic Seal” (QESeal).
  • Support for SSLCOMMERZ payment gateway (SHE-31165)
    • SigningHub now supports the use of a new secure and authorized online payment gateway, SSLCOMMERZ, to perform secured transactions from the customer’s card, mobile wallet or bank account. This will support a one-time payment for Enterprise or Individual Accounts. SSLCOMMERZ is a Bangladeshi payment provider and this enables customers in the region to leverage a local payment provider.


Improvements in this Release

  • Billing Improvements (SHE-33816, SHE-22419, SHE-33963)
    • Auto-recurrent payment is no longer available for "Pay As You Go" plans. However, when the allotted signature quota has been consumed, an alert will be displayed to the user, prompting them to make a manual payment from the Billing screen.
    • Billing expiration is no longer available for "Pay As You Go" and "Pay Regularly" plans. Once a service plan expires. the system will no longer downgrade the user's service plan but will restrict the user from sharing a new workflow or creating an "Only Me" workflow. However, the user can still consume the remaining signature quota.
  • Notify users about completing their respective actions (SHE-33244)
    • SigningHub now displays the information message to each recipient if they navigate away from a document without completing all of their signing actions. This reminds users of any pending actions that they may need to complete on the document(s) and helps to prevent delays in a workflow.
  • Moving Document Package to Custom Folder/Shared Space using Drag-and-Drop (SHE-33689)
    • SigningHub now allows a document package to be moved to a shared space or a custom folder using the Drag-and-Drop Method.
  • Delete the SigningHub instance (SHE-13296)
    • SigningHub now provides an option for Administrators to delete the SigningHub instance which is currently not running.
  • Trust1Connector v3 Support (SHE-32921)
    • SigningHub has been updated to support the latest Trust1Connector v3, this is important for customers in Belgium and other regions who make use of the Trust1Connector to support signing with digital keys and certificates on smart cards and national ID cards.
  • Configure special privileges for each recipient in an Individual Workflow (SHE-24292)
    • SigningHub now provides the Document Owner with an option to configure special privileges (recipient permission, document access security, auto reminders, email language) for each recipient independently in an Individual Workflow type.
  • Send workflow evidence report as an attachment on document deletion (SHE-33394)
    • SigningHub now provides an option at the Administrator level for sending workflow evidence reports of the completed documents to the document’s owner’s email address, in case the document is deleted by the Core thread.
  • Update special privileges for recipients after document sharing (SHE-24485)
    • SigningHub now provides the Document Owner with the ability to change the special privileges (recipient permission & document access security) after a document has been shared.
  • Private comments\messages to specific recipient(s) in the workflow (SHE-30021)
    • SigningHub now provides an option for Document Owners or recipients to post private comments for a specific recipient(s) in the workflow. This enables better collaboration between the signers and ensures that users do not have to leave SigningHub to collaborate on documents that are in progress.
  • Notify all recipients in the workflow on Document Recall (SHE-32165)
    • SigningHub now provides the Document Owner with an option to notify all or only the pending recipient(s) when a document is being recalled.
  • Mandatory Attachments for a Workflow (SHE-32555)
    • SigningHub now provides the Document Owner with an option to mandate specific attachments, to be attached by signers, for documents in a workflow.
  • Shared Enterprise Template to specific enterprise users (SHE-31596)
    • SigningHub now provides the Enterprise Admin with an option to either allow all, any, or none of the enterprise templates, to each enterprise user role. Enterprise users will only be able to view and use the allowed enterprise templates.
  • SigningHub License Viewer (SHE-32537)
    • SigningHub now provides the Administrator with the ability to view the license details.
  • Cancel remote authorisation request (SHE-33293)
    • SigningHub now provides the user with the ability to cancel a remote authorisation request.
  • "Mobile Apps URL" Configuration (SHE-34387)
    • SigningHub now provides the Administrator with an option to configure the Mobile Apps URL which redirects the user to their app. In case the user doesn't have the app installed, it redirects the user to the Play Store/App Store to install the app,
    • The Mobile Apps URL will be used in the following cases:
      • When the user clicks on the "Activate Account" button after opening the "Account Activation" email from their mobile phone.
      • When the user accesses the mobile web and clicks on the "View" button on the mobile web banner.
      • When the user clicks on the "LAUNCH NOW" button on the mobile web during the Remote Authorised Signing process.
  • Pre-authorise Azure AD users (SHE-33637)
    • SigningHub now gives you an option to pre-authorise users in your Azure Active Directory so that they may serve as your registered enterprise users.
  • Message improvement for remote authorisation (SHE-32954)
    • Authentication request alert message that will be sent to your registered mobile device for remote authorisation has been improved.
  • Improved XML document rendering (SHE-32910)
    • SigningHub has been improved to allow uploading of an XSLT Style sheet to transform an XML document into an HTML-formatted PDF document within the SigningHub viewer. This enables users who need to sign an XML to easily view the contents of the XML document.
  • Maintain the Workflow Timeline (SHE-32275)
    • SigningHub now allows the Document Owner and the Enterprise Admin to view the "Workflow Timeline" against a workflow to determine the time each recipient takes to process the document and the total time taken to complete the workflow.
  • Improved logging of actions performed on behalf of a user (SHE-33707)
    • SigningHub logic has been improved to maintain the information about a person/business application who performed any action on behalf of a user.
  • Rerouting to SigningHub (iOS) & (Android) apps for activation (SHE-10654)
    • SigningHub activation logic has been improved to route the user back to the SigningHub (iOS) & (Android) apps where the sign-up process is initiated.
  • Signed by in signature appearance for guest user (SHE-28169)
    • SigningHub now places the correct signer's name for guest users while performing initials, in-person or signature as an individual, delegated or group signer.
  • Display message in case no search result is found (SHE-24880)
    • SigningHub now displays the message 'No record found' throughout the application where no data is returned in case of search.
  • Update email expiry time unit in Account Password Reset email (SHE-23436)
    • SigningHub logic has been improved to show the Account Password Reset email's expiry time in minutes, hour or day units, i.e.
      • If the expiry time is less than an hour, then it should be minutes. Like 50 minutes
      • If it exceeds or is equal to 60 minutes then it should be 1 hour
      • If it exceeds or is equal to 24 hours, then it should be 1 day
  • Language Rename (SHE-35108)
    • The language name for Traditional Chinese ("zh-TW") has been updated from "Chinese" to "繁体中文".
  • Create a user through SigningHub Admin API (SHE-35080)
    • SigningHub now allows the creation of a new individual user through the Admin API.
  • Select between OTP methods independently (SHE-34948)
    • SigningHub now allows you to independently select between OTP via SMS, and OTP via email for authentication during sign-up or log-in, based on your service plan.
  • Special characters in the database connection string (SHE-34316)
    • SigningHub now allows you to use special characters in the username and password of a connection string. (Allowed special characters depend on the selected DBMS)
  • API integration restrictions (SHE-36223)
    • SigningHub now provides the option to restrict a Business Application to only perform actions on behalf of users that are members of defined SigningHub roles.
  • "Change Document Package Owner", "Get Workflow History", and "Download a Document" using client credentials with the user as scope (SHE-35099, SHE-36127)
    • SigningHub now supports changing the document package owner, getting workflow history, and downloading a document using client credentials with the user as scope via the scope API.
  • Account deletion in Mobile Apps (SHE-34946)
    • SigningHub now allows the user to delete their account using SigningHub mobile apps.
  • Bulk Signing Improvements (SHE-34559)
    • SigningHub logic has been improved to allow the user to perform Bulk Signing even when the provided signing capacity does not match the requested levels of assurance. All documents having similar signing capacity will be processed in one go and then the system will notify and ask the user for permission to continue signing the pending documents that require a different signing capacity.
  • CSC Signing Improvement (SHE-35191)
    • From SigningHub 8.4 onwards, at the time of CSC Signing, the system will validate the Key/Status and the Cert/Status. CSC Signing will only be successful when:
      • The Cert/Status is "Valid", and
      • The Key/Status is "Enabled"
  • System-generated Authorization Token flexibility for SigningHub SMS Gateway (SHE-35509)
    • SigningHub logic has been improved to use a system-generated authorization token for the SigningHub SMS Gateway while sending a text message.
  • Performance & Security Improvements (SHE-29794, SHE-34218, SHE-13628, SHE-34303, SHE-34293, SHE-34435, SHE-34303)
    • This release brings several performance and security improvements to different areas of SigningHub including Admin, Authentications, Log-in and Email Notifications etc.
    • Several third-party libraries have been updated to the latest version.
    • SigningHub password reset logic has been improved to not allow the users to not set as password; their full user name, email address or the last used password.
    • SigningHub now verifies the password or OTP, as the case may be, before allowing users to perform any action on a document when "Document Access Authentication" has been configured against a document.
    • SigningHub now displays the link expiry times in DD: HH: MM format, for the following emails:
      • "Reset Account Password" email
      • "Account Activation" email

(However, for the existing enterprise users, this change will take place once the admin resets to default, the "Email Content" in their enterprise settings.)

    • SigningHub API now supports Custom CORS Policy.



Deprecated Features and Important Changes

  1. From SigningHub 8.4 onwards, the auto-recurrent payment feature for "Pay As You Go" plans will no longer be available.
  2. From SigningHub 8.4 onwards, in the case of branded apps, the admin will have to create the Mobile Apps URL and configure it in the admin portal.
  3. From SigningHub 8.4 onwards, to migrate from an API Key integration to a private app for HubSpot, after creating a private app on HubSpot, the admin will have to get the access token from HubSpot and update the API Key in the HubSpot Connector. Henceforth, "API Key" has been renamed to "Access Token".
  4. From SigningHub 8.4 onwards, the existing configured T1C Signing servers will not work and the user will have to configure the API URL, API Port, and Distribution Service URL in the T1C signing connector to make the T1C connector work.
  5. From SigningHub 8.4 onwards, in case you are using an old API Server with the latest version of the SigningHub app:
    • the user will not be able to post any private comments thus all posted comments will be visible to all the recipients.
    • the user will not be able to able to add an attachment.
    • the user will not be able to edit the recipient permissions and document access security for a document package that is no longer in draft mode.
    • the user will not be able to rename a document package that is no longer in draft mode.
    • the user will not be able to configure recipient permissions and document access security for any other recipient except for the first, in an individual workflow type.
  1. From SigningHub 8.4 onwards, in case you are using the latest API Server with an old version of the SigningHub app:
    • the user will not be able to able to add an attachment.
    • if the user switches between an individual workflow type and any other workflow type, the app will display a warning dialog prompting the user that the configured recipients will be deleted.
    • the user will not be able to configure recipient permissions and document access security for any other recipient except for the first, in an individual workflow type.
    • the user will not be able to configure auto reminders for the recipients.
    • the user will not be able to perform the following actions in case "Document Access Security" has been configured against a document:
      • Approve the document
      • Approve the document as a gatekeeper
      • Submit the document
      • Close the document package
      • Fill the form fields
      • Sign the document when any form field is pending

Tested Operating Systems

Operating System

Tested Version(s)

Microsoft 

  • Windows Server 2016, 2019, 2022


Microsoft Windows Server 2022 

Note: TLS 1.3 is enabled by default for installations of Windows Server 2022, integrated applications should support this version of TLS. For application integrations that do not support this and need to be updated, customers can disable TLS 1.3 over TCP in the IIS Bindings. 


Tested Database Server

Database Server

Tested Version(s)

Microsoft

  • SQL Server 2019, 2017, 2016 (Express, Standard and Enterprise Editions) 
  • Azure SQL Database (Database-as-a-service)


Oracle

  • 19c


Customers who are running SigningHub with Microsoft SQL Server 2016, need to upgrade the database instance to service pack 2. To download service pack 2, visit Microsoft's Download Center. 


Supported Upgrades

Ascertia SigningHub 8.4 supports the following upgrade paths:

Upgrades Paths

Steps

7.7.8 to 8.3 

  • Manuals steps are required as mentioned in the SigningHub Upgrade guide - 7.7.x to 8.x.x *


7.7.9 to 8.3

  • Manuals steps are required as mentioned in the SigningHub Upgrade guide - 7.7.x to 8.x.x *


8.0 to 8.3

  • No manual steps are required.


8.1 to 8.3

  • No manual steps are required.


8.2 to 8.3

  • No manual steps are required.


8.3 to 8.4

  • No manual steps are required.


* 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.4 product release. If you require further assistance with upgrading SigningHub, please contact Ascertia customer support.


Supported ADSS Server

Version (s)

Compatibilities

7.1

  • All features are supported


6.9.0.3

  • Add "XADES_SIGNATURE_TYPE" key, with value "ES-X-L", to perform a XAdES Extended signature (SHE-32780)


6.8.0.10

  • Add "XADES_SIGNATURE_TYPE" key, with value "ES-X-L", to perform a XAdES Extended signature (SHE-32780)
  • Reset password for a CSP user without user authentication (SHE-27631)
  • Automatic download of the eSeal certificate from ADSS Server for provided Certificate Alias (SHE-28471)



Compatibility with Earlier Versions of SigningHub

SigningHub (iOS) & (Android) 8.4 are compatible with the 8.3 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