Release 22.R3 (11.48)

What's New

Classic Signing Ceremony

• Classic Signing Ceremony is fully deprecated: The deprecation of the Classic Signing Ceremony began in Release 11.42. That ceremony's API endpoints have now been deactivated, so integrated users MUST now use the API of the Signer Experience. The Classic Signing Ceremony is now FULLY deprecated.

Signer Experience

• Better Electronic Consent workflow: When Change Signer is used, both the original signer and the reassigned signer must now accept the Electronic Consent document. The only exceptions are users who sign via the Personal Certificate Client or a Trust Service Provider. In those cases: (1) if the original signer accepts the Electronic Consent document before changing signers, the reassigned signer will not see that document; (2) otherwise, the reassigned signer will see that document, and must accept it.

• Better workflow for pending signatures: When a Sender is also a signer who has a pending signature in a transaction, a Sign icon now appears next to the name of the transaction. Clicking that icon brings the Sender directly into the Signer Experience for that transaction.

• Can view full document name on each page: When a document is viewed in the Signer Experience, its name appears at the bottom of each page. When a long name exceeds its allocated space there, the name is truncated with an ellipsis. Thus the last part of such names is not displayed. We have mitigated this limitation by showing the full document name when users hover their mouse over the truncated name.

• Can add watermarks to downloaded documents: If a recipient downloads a transaction's documents during the Signer Experience, those documents can be stamped with a customizable watermark that indicates the state of the transaction. The watermark's font, opacity, and position are also customizable. To enable this feature, please contact our Support Team.

Senders

• Can override recipients' language specifications: It’s sometimes useful for a Sender to be able to specify the language of the emails and User Interface that a transaction’s recipients will see, even if the recipients have specified other languages. We’ve therefore created a new account-level flag in OneSpan Sign BackOffice and the self-serve settings for Senders. If that flag is enabled, an account’s Sender can specify a transaction's “recipient language” that will override the recipients’ language specifications. Note: This feature is supported in the New User Experience and the API.

• Can add fields before Signature Blocks: After selecting a recipient, Senders can now add fields to a document without having added a Signature Block. Once a Signature Block is added, all previously added fields will be attached to it. Note: (1) The fields in question are Form-Building Fields (e.g., Text Fields, Text Areas, checkboxes, radio buttons, drop-down lists, labels); (2) This feature is supported in the New User Experience and the API.

• Bulk Send can use large templates: The Bulk Send feature can now accommodate templates that have 300 fields.

• More control over the "next document" button: Before this release, the button that takes a recipient to the next document during the Signer Experience might appear anywhere on a page of the current document. To enable more predictability, we’ve created a new account-level flag in OneSpan Sign BackOffice. When that flag is enabled: (1) that button always appears at the bottom of the page; (2) the button’s text can be customized using BackOffice.

• Easier to deselect delegates: A delegator can now easily stop the delegation of any of their delegates via the Manage Delegation dialog box, which: (1) lists all the delegator’s delegates; (2) displays a Stop Management button that will stop the delegation of a selected delegate.

Account Owners & Managers

• “Account Setting self-service” enabled by default: For all OneSpan Sign accounts (except those created or updated on OneSpan Sign 11.46.x or 11.47.x), Account Setting self-service is now enabled by default for Account Owners and Account Managers. This enables them to immediately configure many BackOffice settings directly from the Sender part of the New User Experience (under Admin > Account Configuration).

Evidence Summary

• Evidence Summary records IP addresses from ID Verification: As a user’s identify is being authenticated via ID Verification, their device’s IP address changes. Starting with this release, the Evidence Summary records those addresses.

• Better button labels: Before this release, the label for the button that downloads the Evidence Summary was causing confusion in some supported languages. For example, in French it resulted in two buttons with different functions presenting the same label – Télécharger (Download). We removed this confusion by ensuring that the button that downloads the Evidence Summary presents a unique label in every supported language.

Virtual Room

• Better video feeds: We increased the size of the Virtual Room's video feed to make it more visible. We also ensured that the system presents only one video feed per participant – i.e., we no longer duplicate the video feed for the person controlling the screen.

• Can select hosts from the Designer: From within the Designer, a Sender can now: (1) select the host of a Virtual Room transaction; (2) send the transaction to its participants. Formerly, if a Sender was in the Designer, they needed to return to the Transaction Edit page to do these things.

Accessibility

• “Account Setting self-service” is accessible: Account Setting self-service is now accessible, so people with disabilities can configure many BackOffice settings directly from the Sender part of the New User Experience (under Admin > Account Configuration).

• Better handling of fields in groups: When fields in a Checkbox Group or a Radio Button Group are added to a document in an Accessibility Enabled transaction, the drop-down list now displays the group name. Users must therefore add the entire group. They can’t add only some of the group’s fields. Similarly, when fields in a group are removed from a document, the entire group is removed.

• Autofields are more readable: We enhanced the readability of pre-filled text in the autofields imported to an accessible transaction’s PDFs.

Bug Fixes

Signer Experience

• PB-85685: Fixed an issue in which confirming a signature triggered a validation error.

• PB-86368: Fixed an issue in which the Download ALL command failed. Such failures occurred because two or more documents had the same name. That situation no longer causes an issue.

• PB-86420: Fixed an issue in which a template with conditional logic shared with other accounts could lead to the following error message when signing: Error: Signing order has been violated.

• PB-85651: Fixed an issue in which the system failed to send a SIGNER_COMPLETE event notification for a transaction after all its required signatures had been applied.

• PB-85044: Fixed an issue regarding signing on mobile devices. The problem was that signers were able to click the Done button before they added a Mobile Signature. This resulted in the system wrongly indicating that a signature had been applied.

• PB-84646: Fixed an issue in which users with no Signature Fields in a document were nonetheless on the list of users “required to sign” the document.

• PB-83078: Fixed the following issue. The Accept banner (prompt + button) for the Electronic Consent document should have appeared at the bottom of the document. Instead, it "floated" at the bottom of the screen.

• PB-84199: Fixed an issue in which the Signature Navigator’s Next button skipped over a required Checkbox Group.

• PB-80908: Fixed an in-person transaction issue in which: (1) Signing Order was turned on; (2) the Transaction Owner was the first signer (3) the next signer couldn’t access the transaction until they refreshed the page.

• PB-85526: Fixed an issue in which the left-pane Navigation Menu failed to open automatically on touch-screen devices.

• PB-87863: Fixed an issue in which an inactive signer session expired earlier than the configured expiry time.

• PB-86027: Fixed the following issue. When a signer clicks the link in their invitation email after the associated transaction has been completed, they should be redirected to the Thank You page. Instead, they were redirected to the Overview page.

• PB-86611: Fixed the following issue. A user signed all their required Signature Fields in a transaction, but subsequently declined the transaction when viewing the transaction's last document, which had no signatures/approvals for the user. At that point, the system presented the user with the following contradictory messages: (1) Please view attached image (decline.png); (2) The transaction has been successfully completed.

Senders

• PB-83421: Fixed an issue in which Bulk Sending operations based on a template failed because the system miscalculated the template’s expiration date.

• PB-80750: Addressed an issue in which the system’s email to a Sender failed to include an attachment containing the Evidence Summary and all signed documents. Now when the attachment’s size is more than 7 MB: (1) this type of email will not include the attachment; (2) the Sender can view the transaction’s documents by clicking a link in the email.

• PB-82852: Fixed an issue in which a 400 error was thrown when an accessible transaction was being created with Text Anchor extraction.

• PB-85547: Fixed an issue in which an error arose when a layout with conditional fields was applied to a transaction with fewer documents and fields.

• PB-84954: Fixed an issue in which removing a signer from a transaction failed to remove the conditional logic related to them. This led to an Unhandled Server Error during signing.

• PB-84692: Fixed an incorrect German translation of text about the Signing Order.

• PB-83151: Fixed the following issue. An error was triggered when a Sender used a Firefox browser to add a Signature Field for a recipient in an accessible transaction.

• PB-82888: Fixed the following issue. When the Designer page was viewed in Chromium/Edge browsers, it was missing the "3 dots" that enable the Documents tab to be opened.

• PB-84990: Fixed the following issue. In a Word document’s embedded creation date, the month was spelled entirely in lower-case letters. When the document was uploaded to a OneSpan Sign transaction, it was converted into a PDF. The problem was that the first letter of the month's name in the PDF was upper-case (e.g., april became April).

• PB-86492, PB-86583: Fixed an issue with the rendering of PDF documents within the application (WebUI). This issue was affecting all browsers.

• PB-85034: Fixed the following issue. When users accessed the Manage Delegation screen on a mobile device, long email addresses on that screen failed to display properly.

• PB-83439: Fixed an issue in which bounced email was recorded as a bounce not just for the email address in the To field, but also for the email address in Cc field.

Admins

• PB-83520: Fixed an issue that was preventing the deletion of roles from sub-accounts.

• PB-74822: Fixed an issue that arose when a role in a sub-account was assigned the permission Transaction visibility for delegates, but the parent account had no assigned roles or permissions. In this situation, the system wrongly allowed users without permissions to view the Transactions and Templates tabs.

• PB-83936: Fixed the following issue. When a transaction’s JSON was viewed in OneSpan Sign BackOffice, it contained no page attributes.

New User Experience

• PB-84926: Fixed an issue in which the Help option appeared in the More Options menu on the User Authentication page, despite the fact that the account-level flag showNseHelp was false.

• PB-84289: Fixed a misleading error message that appeared when users who were required to log in via SSO tried to reset their password.

• PB-85442: Fixed an issue in which the button Skip to main content didn’t work.

• PB-85501: Fixed issues with translations into Chinese (Traditional and Simplified).

Accessibility

• PB-70939: Fixed the following issue. WCAG 2.1 requires that the aria-label of a link or control must begin with the associated visual label. This requirement was not fully met.

• PB-85782: Fixed an accessibility issue regarding font legibility in the Signer Experience.

• PB-83921, PB-83996, PB-83919, PB-83808, PB-83676, PB-83365, PB-81732: Fixed seven issues involving accessible transactions.

• PB-81576: Fixed the following issue involving an accessible transaction. After a signer left the Exit Signing Mode banner, the system focused on the wrong part of the screen.

• PB-81571: Fixed the following issue. After clicking the Enable accessibility mode button, the focus automatically and wrongly moved to the Accept button.

• PB-81562: Fixed the following issue. After a user clicked a Sign button, the Screen Reader failed to provide feedback.

In-App Reporting

• PB-79325: Fixed an issue in which the filename of a transaction report changed from “Transaction_Report_2021_11.csv” before it was downloaded to "___________2021_11.csv" after it was downloaded.

• PB-86024: Fixed an issue with retrieving the filename of an In-App Report via the API. The API input parameter fileName (with an upper-case “N”) did not work, so we changed the code to make it work.

Callbacks

• PB-86972: Fixed an issue in which the system was not forwarding PACKAGE_DECLINED message strings to the Salesforce OAuth2 callback service. Now such messages are always forwarded.

• PB-81969: Fixed the following issue that arose when the signer is also aOneSpan Sign Sender – a Callback Notification recorded the wrong ID in the sessionUser field.

Vaulting

• PB-80732: Fixed an issue that was preventing documents from being registered via OneSpan’s e-Vault Manager Console.

Technology Updates

• PB-85399: Before this release, OneSpan Sign used a Windows-based program to convert documents from one file format to another. To improve font substitutions, OneSpan Sign will now use a Linux-based converter for all supported languages. Note: Some fonts may convert differently in OneSpan Sign 11.48 than they did in OneSpan Sign 11.47.

Known Issues

• PB-85089: Within the New User Experience, we are hiding the permission Manage users' transactions, templates, layouts (API). New clients will never see this permission. If a Sender has this permission today: (1) they can continue to use it; (2) they will no longer be able to see in the New User Experience if they or any other Sender has this permission. If a client wants to enable or disable this permission for a Sender, they must contact our Support Team.

• PB-89179: When an authorized user tries to download multiple In-App Reports, the download is delivered as a zipped file. That file should contain those reports, but instead is empty. The workaround is to download each report individually. This issue will be resolved in Release 22.R4 (11.49).

• PB-86077: An inactive signer session takes longer to expire than the configured time if that time is more than 1800000 ms (30 minutes). This issue will be resolved in Release 22.R4 (11.49).