Release 23.R2 (11.51)

What's New

Remote Online Notarization

• Added ID Verification for RON: Remote Online Notarization now supports the ID Verification authentication method. During ID Verification, a picture of the signer’s ID is shown to the Notary so they can compare it with the signer’s video feed. Fields in the Notary’s Journal are changed to reflect the information that was used during ID Verification.

• Added KBA for RON: Remote Online Notarization now supports the KBA authentication method. This feature must be enabled separately for each account that wants to use it.

• Added a reminder to start recording: At the start of a Remote Online Notarization session, a note about recording the session is now displayed to the Notary.

Signer Experience

• Improved Capture Signature: The Capture Signature panel has been improved in the following ways: (1) the panel now displays the instruction Draw your signature; (2) the signature area now has a background color and a border; (3) signers can now maximize or minimize the panel. Note: Drawing a signature and then resizing the panel will clear the signature. This is expected behavior.

• Split Signature Box: To prevent overlaps among a signature, its timestamp, and its watermark logo, we enabled each of these elements to be displayed in a separate section of the Signature Box. Once enabled, this feature affects all signature types except Click-to-Initial. However, the feature is available only within new transactions.

Senders

• Can add fields not tied to a participant: Senders can now add to a document fields that are not associated with a particular recipient. After a transaction is sent, its participants can see such fields in documents, but they cannot edit them. Note: (1) the values of such fields can be configured only in the Designer; (2) this feature must be enabled either by contacting our Support Team, or by using the Account Setting self-service in the Sender part of the New User Experience; (3) in the Account Setting self-service, this feature is called Imprint fields.

• Conditional fields highlighted more often: In the Designer, fields to which conditional logic applies now display a conditional-logic icon even if the Sender is focusing on an unrelated field.

• Sender UI rebranded: We rebranded the OneSpan Sign logo and colors in the Sender part of the New User Experience.

• Can copy-paste multiple fields at once: In the Designer, Senders can now copy-paste multiple fields at once within the same document.

• Can delete multiple fields at once: In the Designer, Senders can now delete multiple fields at once within the same document.

• Better experience when trying to move fields between documents: Formerly, when a Sender tried to drag one or more fields from one document to another in the Designer, the fields were blocked at the document’s edge, but there was no indication as to why this was being done. Now: (1) a message at the border between the documents states that fields cannot be moved from one document to another; (2) the "blocked" document is grayed out.

Bug Fixes

Senders

• PB-88953: Fixed the following issue. When a Sender used the API to upload a file with an unsupported file name, the system should have displayed a validation error. Instead, it displayed an internal error.

• PB-90376: Fixed an issue in which the system failed to indicate that a transaction's language was the one configured when the transaction was created. This happened after the Sender added a recipient to the transaction from the Designer.

• PB-91545: Fixed an issue in which the Unlock Recipient button mistakenly appeared disabled for a recipient who had been assigned SMS authentication within an in-person transaction.

• PB-89371: Fixed an issue in which an error was triggered when a Sender tried to trash a transaction that had been created from a template with placeholder recipients. This occurred only when the Trash button was clicked from a page that had not been refreshed since the transaction was created.

• PB-90671: Fixed an issue that was causing document pages to be duplicated in the Designer’s Documents panel.

• PB-91637: Fixed a Designer issue in which fields appeared on documents to the left of their assigned positions.

• PB-92211: Fixed the following issue. A Sender used the Designer to: (1) create a transaction; (2) flag one of its recipients as Accept Only. The Sender should not then have been able to add fields to a document for this recipient. However, the Sender could do this. Note: This issue occurred only when the feature No Signature Fields was enabled in OneSpan Sign BackOffice.

• PB-91916: Fixed an issue that arose in the following situation. When a Sender resized a field in the Designer, they made the field extend outside the document (e.g., slightly above the top of the document). This action triggered the following error: Invalid position. Object placed outside of document page boundary. Now, the system performs the resizing without an error, and keeps the resized field within the document.

• PB-72091: Fixed an issue that caused the Designer to crash when Senders uploaded documents whose pages were smaller than letter size.

• PB-91876: Fixed an issue in which the Designer crashed after a Sender selected fields in different documents using Shift + Click.

• PB-91675: Fixed an issue in which the Designer’s Document Preview panel flickered until the application crashed.

• PB-91948: Fixed an issue in which fields on non-active documents in the Designer were not grayed out when fields on the active document were being dragged.

• PB-91122: Fixed an incorrect translation into Portuguese of text about the Bulk Send feature. The correction uses text provided by a native Portuguese speaker.

• PB-93008: Corrected a grammatical error in Japanese on the Transaction Details page.

• PB-92932: Fixed the following issue. A Sender: (1) created an account that had a sub-account; (2) added a user to the parent account, and assigned them a customized role; (3) created a new account, and migrated it under the sub-account. At that point, the existing user should still have had only its assigned customized role. Instead, the existing user had acquired the role of Sender.

• PB-90750: Added missing information in a warning message to Senders. Old Message: This document already contains signature fields. Setting the document as Accept Only will remove all the signatures and data fields that it currently contains. Do you want to continue? New Message: This document already contains signature fields. Setting the document as Accept Only will remove all the signatures and data fields that it currently contains tied to the selected recipient. Do you want to continue?

Signer Experience

• PB-93747: Fixed an issue that occurred when a signer with more than two names (e.g., First, Middle, Last) signed using their initials. The Initials box in the Signer Experience should have displayed all the signer's initials. Instead, it displayed only two.

• PB-91656: Fixed a Signer Experience issue in which a selected date could not be cleared from the Date field.

• PB-91114: Fixed the following issue. When a drop-down list or a Text Field with a height less than 20 pixels was added to a document, it moved down a few pixels after signing was complete.

• PB-91834: Fixed an issue in which a signer who had been assigned only optional signatures failed to receive an invitation email.

Accessibility

• PB-92110: Fixed an issue in which Screen Readers failed to detect Zoom In and Zoom Out buttons in the Signer Experience.

• PB-91405: Fixed the following issue. When users were being authenticated via SMS, Screen Readers failed to read error messages for an expired or incorrect SMS code.

• PB-92358: Fixed an issue in which iPhone users could not enable Accessibility Mode.

• PB-92213: Fixed the following issue. If a user enters a wrong answer when they are being authenticated, a banner notifies them that their response was incorrect . That’s also true in this issue. The problem was that the code accompanying the banner said: role="dialog". This could have confused the users of Screen Readers.

Remote Online Notarization

• PB-90461: Fixed an issue in which a CLEAR button on the Notary Commission dialog box or a Signature Field failed to localize when the language was changed.

• PB-90374: Fixed an issue in which a Notary who had been assigned an optional signature was prevented from confirming a user’s identity.

• PB-90445: Fixed an issue in which a Notary was wrongly listed as a signer when a Journal Entry was downloaded as a PDF.

Delegation

• PB-89895: Fixed the following issue. Before a document was confirmed, a signature failed to display the name of the delegate who applied the signature. Instead, it displayed the name of the original signer.

• PB-89825: Fixed an issue in which the Evidence Summary displayed the name of the original signer for some events, instead of the name of that signer's delegate.

In-App Reporting

• PB-89983: In the column titles of Spanish In-App Reports, we fixed some translation and letter-case issues.

Evidence Summary

• PB-90899: Fixed an issue in which a Downloaded Document entry was mistakenly duplicated in the Evidence Summary.

• PB-92402: Fixed an issue in which the size of Evidence Summary files in the Japanese language were too big (each file more than 8 MB).

Account Owners

• PB-92124: Fixed a broken link on the Account Configuration page.

Developers

• PB-94197: Fixed an issue that caused the sessions of customers using iFrames to expire prematurely. The problem was that the system was failing to fire iFrame Lifecycle Messages (aka iFrame JavaScript Events) in the correct order. To view an example of events fired in the correct order for a typical transaction, see the content under the table in the section Notification Event Types.

Changed Behavior

• PB-89197: By default, the Capture Signature panel now opens in a minimized window. Users can maximize the window if they wish.

• PB-91028: When a transaction’s last document is Accept Only, and the relevant recipient has accepted it (thus completing the transaction), that recipient is directed to the Thank You page. Refreshing that page now leaves the recipient on that page. It used to redirect the recipient to the last document.

• Please note that as of this release (23.R2), you are no longer able to request the activation of the sub-accounts feature. For customers currently using sub-accounts, incidents related to undocumented use cases will be lowered to priority P3 or P4. For priority P1 or P2 incidents related to sub-accounts, we will use commercially reasonable efforts to provide workaround solutions if: (1) the account's use is being impacted operationally; (2) the customer cannot find a root cause of that impact within their own systems; and (3) we determine that a solution for the incident does not require new code. We made this decision to focus on creating enhanced account-management features that will result from an integration with our new OneSpan Transaction Cloud Platform. Please note that you can still request the creation of new OneSpan Sign accounts, and obtain help from our Support Team to configure your accounts.

• PB-89265: We improved the performance of the Signer Experience by modifying the rules that govern the fetching of documents. In particular, in some situations the system will fetch an original PDF instead of a flattened PDF. Fetching an original PDF is faster because it’s stored in cache memory, whereas a flattened PDF is always regenerated when it’s fetched.

  The following paragraphs describe further details.

• Flattened PDFs: Flattened PDFs will be fetched for only the following activities: (1) viewing a signed document whose signatures have been confirmed; (2) viewing an Accept-only document after it has been accepted; (3) viewing a document that was signed or accepted by another recipient before the current recipient accessed the transaction.

  Original PDFs: Original PDFs will be fetched for all these activities: (1) accessing a document (regardless of whether it has been designated for signing, Review-only or Accept-only); (2) viewing a signed document whose signatures have not been confirmed; (3) viewing an Electronic Consent document; (4) viewing a Review-Only document; (5) viewing a document for which: (a) the current recipient has completed all their actions; (b) another recipient still has pending actions (sign or accept).

  Note: As we implemented these changes, we made efforts to preserve callback integrity – i.e., to ensure that customers’ callback integrations will continue to work without modification.

Known Issues

• PB-88685: An error may sometimes appear when changes on the Account Configuration page are saved. If this occurs, refresh the page and try again. This issue will be resolved in a future release.

• PB-91040: When a delegate tries to sign using a signature type other than Click-to-Sign, they may encounter a 403 error. This issue will be resolved in a future release.

• It may require up to 2 minutes for changes on the Account Configuration page to take effect.