Release 5.0

New Features

• OneSpan Sign Embedded Integration for Salesforce senders can now use Recipient Groups that were created in OneSpan Sign.

• Optional Signatures can now be enabled on Transactions.

• Transactions can now be authenticated using a Personal Certificate Client.

• Text tags that were added to a document in OneSpan Sign can now be viewed in OneSpan Sign Embedded Integration for Salesforce.

• A Review Before Completion feature has been added. This allows senders to verify their transactions after all signatures have been collected.

Enhancements

• The OneSpan Sign Embedded Integration for Salesforce Connector now uses the Lightning version of the Salesforce UI.

• To improve performance, the number of recipients that can be added to a transaction has been limited to 30. The number of recipients that can be added using an automation URL is 10.

Bug Fixes

• This release fixes several minor issues that were present in previous versions.

Known Issues

• PB-74847: When a new user profile with no access to Event Notifications is cloned from a Standard User Profile, then the status of their transactions will not be updated if the status update was triggered by callbacks. Ideally, the user shouldn't have access to the Event Notification, but their transactions should be automatically updated to Completed or Declined anyways.

• PB-30099: If you are attempting to attach to a transaction a Salesforce document that has multiple versions  there is no way to know which version of the document you are selecting. Instead, all versions of the document are displayed, with no indication as to which version each file is. As a workaround, users can download the version of the document that they require for the transaction, and then upload the local version to OneSpan Sign Embedded Integration for Salesforce.