Release 24.R2 (11.56)

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 May 9, 2024.

What's New

Signer Experience

• Spanish is now supported for recipients using LexisNexis for authentication: Recipients using LexisNexis for authentication can now receive authentication questions and answers in Spanish.

• Enhanced Transaction Declined Message: If a recipient declines to sign a transaction, thus making the transaction unavailable for other recipients, the remaining recipients will now receive a more detailed explanation as to why the transaction is unavailable to them.

Senders

• Added environment label: When working in a Sandbox environment a small 'SBX' label is now displayed in the upper left-hand corner of the UI.

• Added the ability to set Text alignment: You can now specify the alignment to be used for text within fields, when adding them to a transaction. For example, left, right, center, or justified. In addition, the default alignment can be set to Language dependent, meaning that the text alignment will follow the inherent layout of the transaction's language.

• Streamlined Recipient management: We have improved the way Recipients can be added, configured, and managed when creating or editing a transaction. Senders now have a quicker way of accessing various Recipient settings, resulting in a faster, smoother user experience.

Admins

• Added the ability to upload customized signature logos: Senders can now use the Account Configuration page to upload a customized signature logo for use in their transactions.

• Integrators can now use APIs to upload multiple documents, including Base64 documents: Integrators using either Java or .NET SDKs can now upload multiple documents to a transaction using a single SDK call. This includes Base64 documents.

• Added additional permissions for layout management: Administrators can now add Save Layout and Apply Layout permissions to a role. Note that these permissions will override any configurations made in the Designer, meaning that if, for example, a user does not have the Save Layout permission enabled they will not be able to save layouts, even if the Designer has been configured to allow that.

User Authentication

• Added the ability to make consent explicit: It is now possible to configure IDV transactions so that the consent given by recipients is explicit, meaning that they must actively perform an action to continue. For example, select a checkbox that confirms their consent. If explicit consent is not configured, recipients need only continue with the signing process, as their consent is deemed to have been implied. To configure this, contact our Support Team.

• Added self-serve configurations for OAuth 2.0: Admins can now configure their own OAuth 2.0 authentication settings, using the API Access page.

• Improved the counting of KBA authentication attempts : A KBA authentication attempt will now only be counted if a recipient actually attempts to answer a question. Previously, simply viewing KBA questions would count as an attempt, even if the recipient made no attempt to answer a question. This applies to non-RON transactions only.

Notarization & Virtual Room

• Added the ability to store recipient addresses: Notaries can now store a recipient's address. This address will now auto-populate future transactions and the eJournal if the same recipient is selected.

Trust Vault

• Added detailed information on deleted transactions: Users can now view information about deleted transactions, including the name of the user who deleted the transaction, the name and status of the deleted transaction, the date and time it was deleted, and the names of documents within the deleted transaction.

• Added detailed log information: Users can now view detailed log information related to a document in a transaction. This information includes the name of the user who performed any action on the document (such as downloading it), a short description of the action, the name of the transaction, and the date and time of the action.

Bug Fixes

User Authentication

• PB-99828: Fixed an issue where in certain situations an "Incorrect passcode" error message appeared after a signer had entered a SMS authentication code, but before they had hit enter to register the code.

• PB-101465: Fixed an issue where the data in various IDV columns in the Transaction Reports was not accurate.

• PB-103075: Fixed an issue where switching authentication methods on the Event Notifications page caused the UI to clear any previously changed entries. Now, you can change any entry and your changes will not be lost if you switch authentication methods.

Senders

• PB-92308: Disabled the ability to use Google translate in the Sender UI. Previously, using Google Translate in certain pages would result in an application crash.

• PB-99884: Fixed an issue where Field and Group tooltips were not immediately translated if the Designer language was changed.

• PB-100510: Fixed an issue where the Account Configuration page title was not fully displayed in certain languages.

• PB-100532: Fixed an issue where the KBA status message did not immediately update when changing the UI language. Users would have to refresh the page to see the KBA status in the newly selected language. Now, the field is updated immediately.

• PB-101458: Fixed a translation issue where country codes were not properly translated when using a Polish UI.

• PB-102456: Fixed a date format inconsistency issue. Previously, the date format used to search for transactions, templates, and journal entries did not use the same date format as the format for those entries in their various UI lists.

• PB-102743: Fixed an issue where a signer's name was not displayed in the Evidence Summary for geolocation.

• PB-102934: Fixed an issue where it was possible to paste more than the capped number of characters into the Signer Title field, and the Signer Company field. Rather than not allowing you to enter more than the allowable number of characters the UI would simply cut-off the extra characters upon saving. Now, you cannot paste in more than the allowable number of characters.

• PB-102980: Fixed an issue where the Actions column title in the Groups page was not fully displayed in certain languages.

• PB-103528: Fixed an issue where zooming in and out on a document in the Designer resulted in an inaccurate zoom scale being displayed.

• PB-103576: Fixed an issue that was preventing senders from reactivating expired transactions. This was caused by concurrency issues in the message queue threads.

Accessibility

• PB-98819: Fixed an issue with the alignment of words and sentences in the Electronic Consent Document when Accessibility Mode is enabled.

Signer Experience

• PB-95832: Fixed an issue where there appeared to be a slight delay in the appearance of a second signature field, after the first signature field had appeared. Now, all signature fields appear at the same time.

• PB-101485: Fixed an issue where the Continue button did not appear in transactions with a radio button and an optional signature.

• PB-101828: Fixed an issue where in certain situations a signer was not able to see a document that required their signature. This occurred in situations where an account was configured so as to prevent signers from seeing documents that did not require their signature, AND two signers with the same email address were assigned signatures in two different documents within the same transaction.

• PB-102335: Fixed an issue where an unexpected error was displayed when reassigning fields without a signature to a different signer.

• PB-102980: Fixed an issue where in certain situations clicking Next did not bring a signer directly to a signature field. Instead, the signer was brought to the page with the signature, but then had to scroll through the page to find the signature.

• PB-103178: Fixed an issue where the Signer Experience was zoomed in if an iPhone was used for authentication.

Admins

• PB-103104: Fixed an issue where some transactions were not being purged as per the account's Data Retention settings. This was due to an issue with the SQL query executing the process.

• PB-103115: Fixed an issue where adding a new Role name that exceeded the character length limit resulted in a missing translation error. Now, it is not possible to enter a Role name that exceeds the maximum character length.

Notarization

• PB-97980: Fixed an error where a validation error was shown when changing the type of transaction. This occurred when an IPEN or RON transaction was created with notarial signatures, changed to an IPEN transaction (which resulted in a validation error), and then changed back to an IPEN or RON transaction. In this scenario a second validation error erroneously appeared.

• PB-102099, 102485: Fixed an issue where it was not possible to select a notary with an active notary commission on the day that person's commission expires. For IPEN transactions, a validation error appeared. For RON transactions, the desired notary did not appear in the list of available notaries. Now, these notaries can be selected.

• PB-102072: Fixed an error where attempting to modify the Settings of a Placeholder recipient in a RON transaction caused the system to freeze.

• PB-102598: Fixed an error where it was possible to set a signer from a different account as a notary in your transaction, if that signer was a notary in that other account.

• PB-102646: Fixed an error where a notary signer in an IPEN transaction was not listed as the last signer.

• PB-102649: Fixed an error where the notary waiting room would briefly flash on screen before the notary journal loaded.

• PB-102747: Fixed an issue where an error would appear after changing a RON transaction's journal entry's language to Greek, if that transaction contained a video.

• PB-102748: Fixed an issue where the name of a recipient without signatures was displayed in the eJournal. Recipients who do not have signatures assigned to them no longer appear in the eJournal.

• PB-103306: Fixed an error where the Sign Notary Journal field was not immediately translated if a Sender switched UI language.

Vaulting

• PB-102599: Fixed an issue where a transaction appeared to have been vaulted twice in eOriginal.

Changed Behavior

• PB-98149: Users can no longer be assigned as delegates for other users on another account.

• PB-97276: The signer eid authentication column will be removed for transaction reports generated from June 2024 onwards. It will be replaced with three new columns: signer External Authentication, signer External Authentication type category and signer External Authentication type.

• PB-98153: Users can no longer be assigned the Manager role for a group that they are not part of.

• PB-101225: With the introduction of our new layout permissions it is important to note that when creating a custom role via integration that you must now include your desired layout permissions. You should no longer rely on your existing Transaction permissions to determine whether or not layouts are allowed to be saved or applied. This needs to be done via integration, or through the UI, as this permission is not automatically enabled.

• PB-101993: We have updated the default From and Reply To email addresses of our default email templates. The following From email addresses were added:

  • transaction-notifications@<domain>

  • account-notifications@<domain>

  • system-notifications@<domain>

  The following Reply To email address was added:

  • do-not-reply@<domain>

  The <domain> value is dependent on the environment you are using.

• PB-102456: The date format for transactions, templates, and journal searches has been updated in the sender interface from dd-mm-yyyy to mm-dd-yyyy. Previously, the date format used to search for transactions, templates, and journal entries did not use the same date format as the format for those entries in their various UI lists.

• PB-102774: When accessing a declined transaction, signers will now get a Transaction Declined error page with a specific error message instead of the previous Unauthorized Access error page.

• PB-102421: In order to improve security, we have made the following changes:

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters in any field on the Personal Information section of the My Account page.

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters as the name of an attachment requirement in a transaction.

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters in the Comment field when rejecting an attachment uploaded by a signer.

  • Senders will no longer be allowed to enter greater-than ('>') or lesser-than ('<') characters as the First Name, Last Name, Title, or Company of a recipient.

    These restrictions are applicable when creating or updating an item using the OneSpan Sign UI, or when updating an item using APIs.

Upcoming Changes

• PB-101224: In an upcoming release the API endpoint /api/account/accessibleaccounts will be modified so that using this call will only return the list of sub-accounts that the user making the call has access to. Currently, a list of all sub-accounts is returned.

• PB-103871: In an upcoming release we will update the default From email addresses of customized email templates, but only if the From address is set to an esignlive domain. If it has been modified, or set to a parameter, we will not change it. The following From email addresses will be added:

  • transaction-notifications@<domain>

  • account-notifications@<domain>

  • system-notifications@<domain>

  The <domain> value is dependent on the environment you are using.

Known Issues

• PB-104354: The text alignment feature will always revert to Left in the Signer Title field, no matter what option is selected.

• PB-104459: The IDV Welcome Page event displayed in the Evidence Summary is not translated for certain languages.