Release 24.R1 (11.55)

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 Wednesday, March 5, 2024.

What's New

Trust Vault

• The OneSpan Compliance Vault has been renamed to Trust Vault : All UI instances of OneSpan Compliance Vault have been changed to Trust Vault.

• Transactions and documents can now be searched for and filtered: You can now search your transactions and documents by name, and then filter the search results to view by type (Transactions or Documents), by Anchor Status, and by Owner (if you have permission to view the transactions of other users).

• The Transactions page can now be filtered by owner: You can now filter the Transactions page by transaction owner (if you have permission to view the transactions of other users).

• Used account space is now available: The amount of space currently being used by an account is now displayed in the Trust Vault transaction list. This information is updated as documents are added or deleted.

• Transaction sizes are now available in OneSpan Sign reports: The size of Trust Vault transactions can now be seen in the In-App reports.

• Trust Vault is now available in our Interactive API: Trust Vault schema and responses can now be seen in our Interactive API. To view Trust Vault schema and responses, filter by Trust Vault.

Signers

• Increased length of Signer Title: You can now use up to 127 characters for a Signer Title.

Senders

• Added Created Date column to list of transactions: Transactions can now be viewed and sorted by the date that they were first created.

• PDF tooltips can now be extracted and imported into OSS tooltips: OneSpan Sign tooltips can now be auto-populated with a PDF's existing tooltips. This can be done using Document or Position extraction.

• Can now assign delegates for locked users: In situations where an account has been locked, Administrators and Managers can now assign delegates for that account. This is useful if, for example, a user has left the company.

• Users can now assign Delegates from within the Users page: If Roles and Permissions have been enabled, users can now use the Users page to assign delegates.

Admins

• Searching the Account Configuration Page now returns child settings: When searching for a setting on the Account Configuration page the search results now include any child settings of a search result, even if the child options do not match the search query.

User Authentication

• Reason for authentication failure now included in notification emails: Senders using the email.kba.failure template can now see the reason why a signer failed their KBA authentication. NOTE: If you are using a customized email.kba.failure template then you will need to contact our Support Team to use this feature.

• Added KBA authentication status for LexisNexis users: LexisNexis Senders can now see the KBA authentication status for each recipient in a transaction. For example, Successful, or Failed.

• Added OAuth 2.0 as a possible authentication method for callbacks: OAuth 2.0 can now be used as an authentication method for callbacks.

• Added the ability to define the authentication method used with callbacks: Administrators can now use the Event Notifications page to define the authentication method to be used with callbacks.

• Signers using LexisNexis for authentication now only need to authenticate once: LexisNexis Signers who use KBA authentication to access the Signing Ceremony now only need to authenticate themselves once, instead of each time they access the Signing Ceremony. NOTE: This does NOT apply to Remote Online Notarization transactions. Signers will still need to authenticate themselves when using RON.

• Simplified Evidence Summaries when using IDV for authentication: When using IDV as an authentication method, if the Document Authenticated matcher passes then the authentication is simply noted as having passed in the Evidence Summary. No additional information is provided. If the Document Authenticated matcher fails, then additional information will be provided.

Notarization & Virtual Room

• Can now filter, search, and sort notary journals: You can now use the Journals page to search for, filter, and sort your journal entries.

• Revamped IPEN solution: We have streamlined our In-Person Notarization process to make it more consistent with our Remote Online Notarization process.

• Setting up RON transactions no longer requires KBA for unknown signers: It is no longer mandatory to use KBA when creating a transaction with an unknown signer.

• Improved e-Journal experience: We have enhanced the e-Journal process, making it easier to select document and notarization types.

• Time format can now be configured:The time format for scheduling a Virtual Room session can now be configured to display in either a 12 hour format, or a 24 hour format. For example, 1pm, versus 13:00.

• Updated list of supported Notarization jurisdictions: We have updated our list of Jurisdictions that now support In-Person Notarization.

• Virtual Room and RON sessions will not time-out if a user is performing external authentication: In situations where a signer has been directed to an external resource for authentication purposes, such as to a different tab or web page, their signing session will no longer time-out because of inactivity. Instead, the signing session will time-out 15 minutes after the Host or Notary has left the session.

Bug Fixes

User Authentication

• PB-96559: Fixed an issue where the word "None" was not translated within the KBA provider drop-down list.

• PB-101281: Fixed an issue where the page to enter a phone number to be used for an IDV verification SMS was not appearing.

Senders

• PB-96226: Fixed an issue where the UI would crash when applying a layout where the transaction owner's email was associated with a different role.

• PB-96332: Fixed an issue that prevented users from assigning different languages to duplicate signers. This occurred when adding multiple external signers who have the same email address to a transaction. Attempting to assign a different language to one of the signers resulted in the language being changed for all signers with that email address.

• PB-99437: Fixed an issue which was causing the Save Layout and Apply Layout buttons to become disabled after flagging a recipient as a reviewer (Accept Only).

• PB-99395: Fixed an issue where the Sender UI allowed users to enter an empty space in the First or Last name fields. For example, by hitting a keyboard space bar. You must now enter a first and last name.

• PB-99440: Fixed an issue where a sender was not receiving the email.transaction.complete email. This occurred when a signer order had been set, and the sender was the last signer.

• PB-99752: Fixed a labeling issue for both Chinese Traditional and Chinese Simplified languages.

• PB-99754: Fixed an issue affecting Apple devices which caused documents in the Signer Experience to appear blurry or pixelated, disappear, or even crash completely.

• PB-99890: Fixed an issue where the expiry date for a transaction appeared in the Inbox for a transaction with a Draft status. This occurred when setting an expiration time in days. Transactions that are in a Draft status do not expire, and thus there should not have been a specified expiry date.

• PB-99955: Fixed an issue which made fields disappear when the transaction expired while still having an In Progress status.

• PB-99970: Fixed an issue where the Date field's size changed. This occasionally caused the field to change positions in a document.

• PB-99993: Fixed an issue where the French expiry date was not translated correctly within the email.delegation.activate email template when there was no expiry set for the delegation.

• PB-100010: Fixed an issue that was preventing the use of SMS authentication when the Sender had selected a non-existant country in their My Account profile.

• PB-100119: Fixed an issue where creating conditional fields using an API resulted in duplicated conditions when field names had matching starting characters.

• PB-100157: Fixed an issue where it was not possible to delete a field with conditional logic.

• PB-100158: Fixed an issue where the message "Expiry scheduled for null" appears in the UI when creating a transaction using a template with an expiration set for a number of days.

• PB-100312: Fixed an issue where the Sandbox watermark appeared twice on the French version of the Electronic Consent Document.

• PB-100367: Fixed an issue that was preventing integrators from updating or removing a Decline Reason using a PUT API call.

• PB-100442: Fixed an issue where changes to the expiration date, from a set date to unlimited expiration, are not remembered when creating a transaction from a template.

• PB-100483: Fixed an issue where users were allowed to enter an incorrect date when adding a delegate.

• PB-100515: Fixed an issue where an incorrect expiration date appeared on a template. This occurred when enabling and then disabling the Unlimited Expiration checkbox.

• PB-100618: Fixed an issue where you were not able to add a Placeholder type recipient from the Designer.

• PB-100647: Fixed an issue that caused issues with accessing FedRAMP Production environments.

• PB-100736: Fixed an issue that was preventing users from accessing the Transactions page.

• PB-100799: Fixed an issue where transaction owners were not able to download documents from their own transactions if the Display Download button setting in the Account Configuration page had been disabled. Transaction owners can now download their own transactions even if this setting is disabled.

• PB-101207: Fixed an issue where the search within the Inbox was not returning results when there was a very large number of transactions.

• PB-101145: Fixed an issue where customized roles could be assigned to users under different accounts. Customized roles can now only be assigned to users in the same account.

• PB-101206: Fixed an issue where in certain situations the Transactions Inbox would not display if Layouts had been disabled for the account.

• PB-101439: Fixed an issue where the SIGNER_COMPLETED event was not sent for a sender when a transaction with both Review Before Completion and a signing order were enabled.

Signer Experience

• PB-99591: Fixed an issue where text on certain documents appeared highlighted when accessed in the Signer Experience using older versions of iPhone iOS.

• PB-101521: Fixed an issue where Signers were experiencing Unauthorized Access errors. This was caused by an invalid token in the signing URL.

Admins

• PB-96623: Fixed an issue where the placeholder text and labels were not correctly translated on the Account Configuration page until the page was refreshed.

• PB-100235: Fixed an issue preventing admins and managers from assigning delegates for migrated sub-account users.

Vaulting

• OCV-657: Fixed an issue that was causing the dates and times that appeared in a Trust Vault Proof Certificate to display in English, even if the certificate itself was in French or Spanish.

• OCV-742: Fixed an issue where users were unable to delete their own transactions even if they had the Access and Delete Own Transaction permission enabled.

Accessibility

• PB-35943: Fixed an issue where there were no header labels for the input fields when adding recipients to a transaction.

• PB-93777: Fixed an issue where the error message that is sent when an invalid answer is provided in response to a Q&A authentication was not being read in full by certain screen readers. This occurred when using Windows 11 OS and iPhone 12 iOS.

• PB-96351: Fixed an issue where the sub-sections on the Account Configuration page were not being announced by screen readers. For example, Feature Settings > Email Documents.

• PB-99538: Fixed an issue where the More Actions menu button in the Signer Experience did not meet accessibility standards.

• PB-99602: Fixed an issue where field buttons in the Designer were not being announced by certain screen readers.

• PB-99604: Fixed an issue where tooltips were not being read by certain screen readers.

• PB-99605: Fixed an issue where the purpose of an asterisk next to a field was not being explained by screen readers. An asterisk next to a field indicates that this field is required, but this was not being announced by the screen reader. Now, the following text appears in the UI and can be read by screen readers: "Fields marked with a * are required".

• PB-99607: Fixed an issue where tab names (Drafts, Inbox, Trashed, Archived) were not announced by the JAWS screen reader on the Transactions page.

• PB-99608: Fixed an issue where table names were not defined and therefore not listed when accessing the Tables shortcut in the JAWS screen reader.

• PB-99991: Fixed the color contrast of the sign icon within the Transaction List so as to meet accessibility requirements.

• PB-101667: Fixed an issue where there was a discrepancy in the timestamp of the signing date when accessibility mode is enabled, versus the timestamp of the signing date when accessibility mode is disabled.

Performance Improvements

• PB-98332: Improved the performance of the Designer when using a document with a significant number of fields and conditional logic applied to it.

• PB-100941: Improved the performance of the Signing Ceremony during situations where a high volume of transactions that needed to be signed by a recipient occurred. Previously this resulted in a high CPU Load warning.

• PB-100355: Improved the performance of our Transaction Inbox.

• PB-100801: Improved the performance of our Dashboard.

Changed Behavior

• PB-93646: The PDF base-14 fonts Courier and Helvetica are now replaced in PDFs by the fonts LiberationMono and Liberation Sans, respectively. This ensures that these fonts will be embedded in the PDF, and that documents will look the same across all PDF viewers and operating system platforms. Note that this is only relevant for text form fields, watermarks, and signatures. The actual text of a document is not affected.

• PB-98498: The Event Notifications page now has a drop-down menu that can be used to select an authentication method. NOTE: If no Callback Key has been defined the authentication method will be set to None. If a Callback Key has been defined, then the authentication method will be set to Basic. In addition, OAuth 2.0 is now available as an authentication method.

• PB-99395: When editing your My Account information, a first and last name is now required. For existing Senders who were created without a first or last name, you can not edit those Senders without adding a first or last name.

• PB-101707: Upon completion of an In Person Notarization (IPEN) session a notary can now click a button and be redirected to their e-Journal.

• PB-100793: It is now possible to turn off enforced authentication for RON and IPEN transactions.

Upcoming Changes

• Our Text Alignment feature will not be deployed in Release 24R1 (11.55) Production environments, but will be available in a future release.

• In Release 24.R2 (11.56), all references to Equifax will be removed from the code base. Any integration code (APIs and SDKs) that references Equifax as a recipient authentication method will need to be removed.

Known Issues

• PB-99976: Using the Designer to set a default value for text fields higher than 1024 characters results in an error message. However, if you set the default value to 1024 characters your signers can still enter up to 4000 characters in the Signer Experience.