Skip to main content

Autumn release 1.19.1

Support | ValidSign
  • Updated

What's New

  • Added the ability to automatically extract signatures and fields by placing Text Tags directly in a document. ValidSign will analyze the uploaded document, and replace every text that matches the Text Tag pattern with the appropriate signature or field.
  • Qualified Certificate Signing to all supported browsers on Microsoft Windows.
  • The Evidence Summary now records when a transaction owner manually completes a transaction.
  • As soon as a sender completes signing a transaction, they are now prompted to proceed to the next transaction.
  • Implemented quicker access to the Signing Ceremony. The application will determine if it is your turn to sign. If so, it automatically launches the Signing Ceremony when you click on a transaction from your Inbox. This applies to all transactions awaiting your signature.
  • Added support for optional signatures. This permits a signer to complete a transaction without signing all of their signatures inside the transaction's documents. Any signature type can be flagged as "optional" via the New User Experience, the REST API, or the SDKs. 
  • Enabled account owners to retrieve their integration API key via the Administration menu.
  • As part of an ongoing effort to make the New Application User Experience accessible to visually impaired senders:
    • The color scheme was improved for visually impaired senders.
    • The Dashboard's Account Summary chart was made a non-clickable image. Instead, the items within the legend indicate the number of transactions, and they link to the Reports page.
    • The following changes were made to the Date Picker control:
      • Dates can now be input manually.
      • Senders must now click OK to confirm their date selection.
      • To clear a date, you must now do one of the following: (a) select the date and press DEL on the keyboard; (b) open the calendar, and click Clear.
  • One-Time Password (OTP) codes for SMS Authentication will now expire within 5 minutes.
  • A user can now change the signer's Company and Title when they delegate signing to another user.
  • Links that appear in PDF documents can now be de-activated for an account.
  • Document deletions are now recorded in the Evidence Summary.
  • Optimized the Package Overview API, thereby improving overall performance.
  • Enhanced performance by enabling the Documents call to be executed more rapidly.
  • Added customizable time zones for transaction owners at the Account, Sender, and Transaction levels. Thus the time zone used to display all dates on a transaction's signed documents can now be customized.
  • When a callback fails, an email is sent out. That email has been improved to include the reason for the failure.
  • Added Android and IOS talkback support for the Mobile Signing Ceremony on tablets.
  • Enabled blind and visually impaired users to review and click-to-sign PDF documents on mobile devices. This involved making the Mobile Signing Ceremony support Web Content Accessibility Guidelines (WCAG) 2.0 Level AA.
  • Enabled Bulk Signing — "Sign All" — for: (1) the Signature Capture signature type; (2) documents with mixed signature types.
  • Made SMS messages more customizable than they had been.
  • Enabled static hyperlinks in PDF documents that are in a completed transaction.
  • Enhanced Single Sign-On (SSO) Authentication to support external recipients. This enables the exchange of authentication information between ValidSign and corporate servers. Thus signers can now use their organization's credentials to access the Signing Ceremony.
  • Ensured that the Owner of a transaction receives a notification every time a signer uploads an attachment. This is especially important if a rejected attachment is re-uploaded.
  • Added the names of Form Fields to the Audit Trail section of the Evidence Summary document.
  • Enabled the Enforce Signature Capture option to be set at the signature level. 
  • Signers and senders can now choose to view ValidSign in Danish and Portuguese. This support includes email templates, in that transaction owners can specify Danish and Portuguese as the language to be displayed to an individual signer.
  • Enabled transaction owners to configure reminders for all recipients of a transaction who have not yet signed.
  • Enabled the Signing Ceremony to: (1) detect when a user's Internet connection is lost; (2) prompt the user to reestablish an Internet connection, and then continue the Signing Ceremony.
  • To address security and end-of-life issues, we updated the third-party libraries used by the Java SDK.
  • Introduced an Accessibility Support component that enables blind and visually impaired signers to review and click-to-sign PDF documents. Gave account owners more control over the Email, Q&A, and SMS Signer Authentication options for their account. Before this release, senders could assign any of these methods to a given signer. Now, account owners can limit their senders' choices (e.g., by forbidding the Q&A method on their account).
  • Enhanced the Mobile Signing Ceremony by enabling the redirection of signers to a customized external page when their session expires.
  • Enhanced the SDK by enabling a single request to upload multiple documents to an existing transaction.
  • Enhanced the Mobile Signing Ceremony by removing the need to click a Signature Box to bring it to the foreground. Signers can instead magnify a Signature Box by using the built-in pinch-to-zoom capability of their mobile device.
  • Enabled the system to efficiently handle a larger number of documents within a transaction. This fix reduces the time needed to navigate between documents or to sign documents.
  • For the Mobile Signing Ceremony, we implemented optimized pages for the Q&A and SMS Authentication Methods. Previously, these methods directed mobile-device users to desktop authentication pages that were not optimized.
  • Completed all preparations for disabling TLS 1.0. For the associated schedule and expected impacts.
  • Extended label customization to the Mobile Signing Ceremony. The messages that will appear to signers during that ceremony are now fully configurable at the Account level..
  • Enabled the Apple Pencil to be used in the Signing Ceremony.
  • Enabled the Callback timeout to be configured to give the Callback endpoint extra time to process a Callback request.
  • Now when a user signs with a mobile device, optional signature are available in the Mobile Signing Ceremony.

Browser Support

  • As of Release 11.22, the New User Experience will no longer support Internet Explorer 9 or 10.

Performance Enhancements

  • System throughput (number of transactions per hour supported by the system) has been improved by 25%.
  • The Get Package API response time has been reduced by 13%.
  • The load time for the API underlying the Dashboard's Account Summary pie chart was improved by 36%.