Release 24.R5 (11.59)

For information on our current and upcoming deployments for this release, please see the Releases and Maintenances Calendar section of our Trust Center.

These Release Notes were last updated on September 26, 2024.

What's New

Here are some of the new features and enhancements we have made for this release.

Design Change Advisory - ADA Compliant Designer

The Designer page has been improved for a cleaner user experience and to meet ADA requirements: (refs PB-99115)

• We have revised the color palette of recipient fields to meet WCAG 2.0 compliance standards. We have enhanced the readability of the text within those fields by using lighter colors to increase the contrast between the text and its background.

• Fields now display the default value for the field, instead of the field type. In addition, the Signature and Initials fields now display only the signature type, so as to emphasize the action the signer should take. This is to give Senders a better idea of the text alignment of the Sign button text that recipients will see in the Signing ceremony.

• Our field icons have been updated.

• The field settings panel now displays the field type, and has been updated with the new icons.

Admins

• Ability to limit languages: Administrators can now limit the languages that can be used for signing transactions. With this feature you can now define the a list of supported languages that can be used during the New Signer Experience, as well as specify a default language for signing. This allows you to control the branding and white labeling of your transactions. (refs PB-102382)

• Improved performance and logging of callback failures: We’ve improved logging to make it easier to trace callback failures. We have also made some technical improvements that will lead to better performance. (refs PB-105747)

• Enhanced System Updates Log Reports are now available: You can now use our APIs to retrieve logs related to account configuration events. These reports are generated as .csv files. To test these features, see our Interactive API Reference. The following events can now be retrieved: (refs PB-106227)

  • Feature setting updates

  • Transaction setting updates

  • Security setting updates

• A New Delegation Log Report is now available: You can now use our APIs to retrieve logs related to delegation events. These reports are generated as .csv files. To test these features, see our Interactive API Reference. The following events can now be retrieved: (refs PB-106419)

  • Delegation creation

  • Delegation editing

  • Delegation deletion

Evidence Summary

• New verification error messages: There is now a new error message that appears when authentication fails due to an unsupported document, or a document that failed to process. (refs PB-100036)

• The verification results tables can now be sorted alphabetically: The Matcher column in the verification results table can now be sorted alphabetically, to make it easier to find the information you are looking for. (refs PB-102952)

Integration Platform

• New workflow integrations: We have added new integrations to connect eSignatures to your favorite business applications. The following new integrations have been added (refs PB-105335):

  • OneDrive

  • Dropbox

Notarization

• We have switched audio-video providers: Beginning with this release we will be using Vonage as our audio-video provider, instead of Twilio. (refs PB-104371)

• Florida and Indiana now support Remote Online Notarization: Using the RON is now legally accepted in the states of Florida and Indiana. (refs PB-105903)

• Notary training videos now included in invitation email: Once your account has been updated to enable RON and IPEN transactions you will receive an onboarding email that now includes a link that quickly requests access to our Online Learning Academy and our Notary videos. (refs PB-106864)

Senders

• There is now a simpler way to change a recipient's type: Changing a recipient's type can now be done directly in the Designer, without having to move back to the transaction page. This allows you to easily make recipient type changes, such as replacing placeholders before sending the transaction before signing. (refs PB-106694)

Signers

• New Authentication Sign-in page: Signers that have an associated authentication method are presented with an introduction page on accessing the signing ceremony, informing them that they will need to authenticate before continuing. This page is now displayed by default for esigning and in-person transactions where the authentication method is set to any of the following: Q&A, SMS, Q&A+SMS, or KBA. Note that this page cannot be disabled as it allows signers to explicitly consent to the authentication process and it prevents virus scans and preview applications from triggering unwanted authentication requests from a recipient's email inbox. (refs PB-106194)

Bug Fixes

The following issues were resolved in this release:

Admins

• When searching for a sender's template using an API call a 403 error would sometimes appear. This happened when searching for the template using the sender's email. Searching for a template using a sender's email was case-sensitive, meaning that if an improper case was used in the search parameters the template would not be found. We have fixed this so that this specific search is no longer case-sensitive. (refs PB-107800)

Evidence Summary

• We have fixed an issue where the wrong IP address would show when completing an IDV journey. (refs PB-106780)

• If a signer accessed the Signer Experience from two different countries the evidence summary would report only one IP address. This has been fixed so that the evidence summary now shows both IP addresses. (refs PB-107644)

Senders

• Attempting to copy, paste, and move the same field created performance issues and errors. This has been fixed. (refs PB-106784)

• Transaction with mandatory attachments cannot be set to autocomplete. However, it was possible to edit a transaction via API and set autocomplete to true, even if there were mandatory attachments in the transaction. This made it possible to complete a transaction before the mandatory attachment had been uploaded. This has been fixed and is no longer possible. (refs PB-108170)

Signer Experience

• When editing a transaction by adding or removing documents, signers would sometimes be redirected to a document that was not next in the signing order. This document would not have any signature fields for them to sign. This no longer happens. (refs PB-107200)

Upcoming Changes

Here are some of the new features, changes and enhancements that we will be introducing in an upcoming release.

• In an upcoming release, some validation will be added to the Signer phone number input (via PUT and POST API calls) and to the Sender phone number input (under My Account > Personal Information). The following changes will be made (refs PB-104448):

  • Input will be restricted to a maximum length of 15 characters

  • Alphanumeric characters will be allowed

  • The following special characters will be allowed: + - # ( )