Release 25.R1 - Coming soon!

Changed Behavior

Here are some of the changes in behavior that you might want to be aware of.

• Signers who are also account senders, will now join in-person signing sessions as signer and not as a host: When a Signer, who is also a Sender of the account, accesses an in-person signing session from an email invitation, they will do so as a signer and not as a host. This will happen even if the "Allow account senders to host in-person esigning transactions" feature is enabled for the account. The current behavior will remain unchanged when the Signer is the transaction owner, meaning that Senders will still be able host the transaction if they are the ones to initiate it from the Sender UI. (refs PB-109998)

Upcoming Changes

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

• For security reasons we will no longer allow Signers to use HTML code in the Reason field when declining a transaction. (refs PB-108289)

• Similarly, we will no longer allow Senders to enter HTML code in the Message to all recipients and Personal Message fields of a transaction. However, this can be enabled by contacting our Support Team. (refs PB-108287)

What's New

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

Admins

BETA - Ad hoc groups can now be created: Ad hoc groups are useful for when you would like to create a group, but for a single transaction only. For more information, see Ad Hoc Groups. (refs PB-108433)

This feature is currently in BETA and only available for Sandbox environments.

BETA - A Transaction Analytics Dashboard is now available: Administrators can now use our intuitive transaction dashboard to analyze transaction performance. (refs PB-108163)

This feature is currently in BETA and only available for US Sandbox environments.

This dashboard provides the following:

• An overall view of transaction performance

• Transaction trends

• Transaction status by sender or transaction

Also note the following:

• This feature is only available for users with Admin or Manager roles, or users with the Reports permission enabled for them.

• To enable this feature you must contact our Support Team.

• Data is currently restricted to transactions that were NOT purged or deleted in 2024. Starting next year, all transaction data will be available.

Authentication

Early Access to FIDO Passkeys for Signers: When accessing a transaction requiring their signatures, signers can now add Passkeys to authenticate themselves. Passkeys are a modern, secure way to log into transactions without using traditional methods, such as Q&A, SMS, and standard passwords. In the passkey system, a cryptographic key pair is utilized: one private key is kept on the user's device, while the corresponding public key is stored on the server of a website. The private key remains confidential, thereby minimizing the chances of phishing attacks or credential compromise.

To get early access to this feature please get in touch with your customer success manager or contact our Support Team. We are looking forward to hearing your feedback!

For more information, see Using Passkeys. (refs DAG-26)

Bug Fixes

The following issues were resolved in this release:

APIs

• The dates returned by the GET packages and GET packages/packageId calls now match. (refs PB-109475)

Authentication

• The Evidence Summary now displays IDV supplemental information using the signing order from the Audit Trail. (refs PB-102951)

• We have improved the error message that is used for unsupported documents. (refs PB-108425)

Senders

• On larger documents the scrollbar slider in the Designer was too narrow, which made it difficult to scroll. The scrollbar now increases in size when hovered over. (refs PB-110633)

• We have fixed an issue where delegate emails were not being sent out if one of the delegate's email address had been blacklisted. (refs PB-111513)