If you are upgrading to this version from a previous installation, you must follow the instructions described in Upgrading to 5.0.
- OneSpan Sign 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 for Salesforce.
- A Review Before Completion feature has been added, which allows senders to verify their transactions before sending them.
- The OneSpan Sign 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.
- 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 for Salesforce.
If you are upgrading to this version from a previous installation, you must follow the instructions described in Upgrading to Version 4.12.
- The OneSpan Sign for Salesforce Connector has been rebranded with our new OneSpan corporate identity.
- New colors, layout, and design.
- Terminology changes:
- "eSignLive for Salesforce" is now called "OneSpan Sign for Salesforce"
- "Signers" are now called "Recipients" in some instances, though both may still be used interchangeably.
- "Packages" are now called "Transactions"
- The displayed language for a transaction can now be configured by an Administrator.
- Users can now manually send email reminders.
As with SaaS deployments, multiple Salesforce organizations can now connect to an on-premises (or private cloud) instance of OneSpan Sign.
- The number of signers that can be added to a transaction has been increased to 100.
- The signer authentication methods, SMS and Question and Answer, can now be set via a custom button in Salesforce.
- Attachments and File object records are now displayed as related object attachments.
Package Synchronization, introduced in 4.11 has been extended to retrieve signed documents and update Signer status as well.
- PB-22320: This issue only occurs on Internet Explorer. When preparing a transaction, suppose you delete a document and then return to the transaction page to add another document. Once you return to the Designer , the document preview pane will still show the original, deleted document. To replace this document preview with the correct one, try refreshing your browser, or closing and then re-opening Salesforce.
- PB-10617: If a user has been locked, the status of the locked recipients is not displayed on the Transactions Home Page. However, the correct locked status can be seen when viewing the transaction's details.
- PB-15515: OneSpan Sign for Salesforce cannot be installed if Shield Platform Encryption has been enabled. For more information see Which Salesforce Apps Don’t Support Shield Platform Encryption? To fix this issue, use the following workaround:
- In Salesforce, open the Setup page.
- Using Quick Find, search for Platform Encryption.
- Click Advanced Settings, and then the Deterministic Encryption checkbox.
- In the Platform Encryption section, go to Encryption Policy.
- In the Encrypt Fields section, click Edit.
- Select Emails and change the Encryption Scheme to Deterministic.
- Salesforce System Administrators can now synchronize package status on-demand. In particular, they can update the status of packages in Salesforce with their status in OneSpan Sign. For details, see Synchronizing Salesforce Package Status with OneSpan Sign.
- Added five new columns to the Event Notification tab (Package Name, Salesforce Object ID, Owner, Error Message, and OneSpan Sign.com ID).
As with SaaS deployments, multiple Salesforce organizations can now connect to an on-premises (or private cloud) instance of OneSpan Sign.
- CONN-241: Fixed a writeback issue. Formerly, after a signer completed signing a package, the system failed to return to Salesforce the values entered by the signer in OneSpan Sign fields during the Signing Ceremony. Now the system does this.
- CONN-4767: We fixed an issue that was preventing the OneSpan Sign for Salesforce connector from receiving callback information for Document Signed, Signer Complete, and Package Complete events.
We encountered a Salesforce issue that impacts the "new feature" described above. In particular, Salesforce will not do a "partial commit" to its database. Salesforce has been informed of this issue, and they are currently working to fix it. For more information, click here.
- MAIN-1924: The Configuration tab of the OneSpan Sign Admin page in Salesforce displays a parameter called IP Restriction. That parameter's description contains a link called OneSpan Sign IP addresses that is currently broken. That link should connect to this page.
- Formerly, end-users and integrators could add documents to OneSpan Sign packages and templates using Salesforce Notes and Attachments objects. Now they can also add documents using Salesforce Files. This can be done either via the GUI (see Step 6 of the procedure Adding Documents to Packages and Templates) or via code (see the Documents parameter in Parameters for URL Code Snippets).
Added custom logs to track all OneSpan Sign callbacks. This will help our Support Team solve customer issues by gathering all information about a package's status.
- The maximum length of the "related object name" of the OneSpan Sign object package was increased from 50 characters to 255.
- CONN-150: We increased the maximum length of the OneSpan Sign package name from 50 characters to 80 in the package automation routine.
- ESSF-2028: We improved the "Apply Layout" functionality as follows: (1) if users apply a layout that has more Signer Roles than package signers, an appropriate number of "signer placeholders" is added to the package; (2) if users apply a layout that has the same number of Signer Roles as package signers, no placeholders are added.
- ESSF-2045: We clarified and simplified several error messages.
- ESSF-2044: When you're using a Salesforce government Cloud instance of OneSpan Sign for Salesforce, the Save Layout button does not appear on the Prepare page. As a workaround, users can create, save, and share a layout by going to a OneSpan Sign government Cloud instance.
- ESSF-2089: When a layout is applied, if a signer does not exist in the associated package, the software creates a signer "placeholder". However, if you try to replace such a placeholder with an actual signer, you may not see that replacement unless you refresh the page.
APP-5291: When the Salesforce connector is connected to the website of the OneSpan Sign New Interface (v11), users see the following message when they activate a template: Error: Cannot access a deleted package. As a workaround, the package can be auto-prepared using layouts or Signer Label and Text Tag Conventions.
APP-5515: This concerns a situation in which the Salesforce connector is connected to the website of the OneSpan Sign New Interface (v11). When users enter the phone number of a signer for Signer Authentication via SMS, they must use the following format: [+] [country code] [subscriber number including area code].
- Before this release, OneSpan Sign for Salesforce could not connect to eSignLive for Government (a FedRAMP-certified eSignLive environment). With this release, Salesforce Administrators can configure OneSpan Sign for Salesforce to OneSpan Sign Sandbox for Government.
- When OneSpan Sign for Salesforce is installed in a Salesforce government Cloud instance, Salesforce users cannot upload documents from their computer to a OneSpan Sign package using Internet Explorer. As a workaround, users may upload documents using another type of browser.
- Enabled Admins to connect OneSpan Sign for Salesforce to the following environments:
- OneSpan Sign Australia and OneSpan Sign Europe
- eSignLive for Government (a FedRAMP-certified eSignLive environment)
- A client-configurable OneSpan Sign environment URL. OneSpan Sign clients can use this option to connect OneSpan Sign for Salesforce to their own instance of OneSpan Sign.
- Improved behaviour regarding the failure of the Admin OAuth token to refresh.
- Ensured that the Status of Signers and the Package Status match when a package is programmatically created and sent from an object.
- Integration of Chatter provides users the ability to use the built-in Salesforce notification system to be notified when a package is modified.
- Support for the Salesforce Lightning Experience.
- Support for the OneSpan Sign field types: Radio Buttons, Lists, and Labels for Auto-Prepare (Text Tags) and Auto-Population (Insert and Write-Back).
- International phone numbers are now supported for SMS Authentication.
- Enhancement to the Clone a Convention feature now clones the associated Field Mappings, Signer Labels, and Text Tags that are included in a convention.
- Added a Save & New button for the Create Text Tag feature to simplify text tag creation.
- Improved the Instructions tab of the OneSpan Sign Admin page.
- If the Salesforce Admin that originally connected the application to Salesforce no longer has a valid authentication token (i.e. if it has expired), OneSpan Sign is not able to connect to Salesforce. The Admin will first have to disconnect the OneSpan Sign application from Salesforce via the Admin page, and connect it again with a valid authentication token. This action will refresh automatically the authentication token.
- If the Salesforce Admin logs in as another user via the Users list, they will be unable to use the application. To fix this, log out and log back in via the Salesforce login page.
- OneSpan Sign for Salesforce supports the Lightning Experience in Salesforce, but certain page layouts and procedures may be different.
- If the default consent agreement is disabled on your account, an error would occur when the user attempts to reorder documents in prepared packages and templates.
New User Licence Information: With OneSpan Sign for Salesforce, by default there is one user license per account. The default licence includes a free trial of 30 days for 1 user.
Fixed the following issues:
- When using auto-prepare, users can add multiple signature blocks for a single signer.
- Users can define text anchors with negative offset values (up and left from the text anchor).
- Users of Salesforce Pro Edition can upload documents from their local machine (maximum document size is 2 MB).
- Users can now use OneSpan Sign for Salesforce when "
Salesforce to Salesforce" is activated.
This is a maintenance release of OneSpan Sign for Salesforce providing support for the release of Salesforce Winter '16 with the Lightning Experience disabled.
- With the Lightning Experience enabled, users become stuck on a page when preparing packages and templates, and attempting to sign documents.
- Field Mappings are a new OneSpan Sign Convention type that allows the package creator to insert data stored within Salesforce into OneSpan Sign form fields, as well, can collect additional information about a signer at the time of signing, and to automatically have that information written back to the Salesforce contact.
- The new embedded Designer and Signing Ceremony user interface enables users to prepare, send, and sign OneSpan Sign documents, as well as prepare and activate OneSpan Sign templates within the same browser page as Salesforce.
- Save and Apply Layouts is a feature that is added to the embedded designer page.
- Users can configure the embedded designer and signing ceremony links or enter a custom application name.
- Track signing status allows users to track the signing status of each signer from the package or related objects page.
- Change Signer is an option that allows signers to delegate their signing authority to other signers. Users can allow multiple signers to delegate their signature when they create a package or a template.
- Administrators can now use their OneSpan Sign credentials to connect the application to their OneSpan Sign accounts after a new installation without needing an API key. This feature does not impact the organizations that are upgrading a previously installed application. Applications which were connected to a OneSpan Sign account will remain connected after an upgrade.
- Users can now view the Electronic Evidence Summary for completed packages from the package page.
- Administrators have the option to Enable Package .zip creation to give users access to a zip file that includes a copy of all signed documents. This feature is disabled by default.
- This release enables package owners to unlock signers due to too many failed authentication attempts.
- User Experience Enhancements:
- Packages and Package Templates have been renamed to OneSpan Sign Packages and OneSpan Sign Templates respectively.
- The Edit button for sent packages has been renamed to Recall to reflect that the package is unavailable to signers until it is sent again.
- A number of new tooltips have been added throughout OneSpan Sign for Salesforce that provide more information as to what an options does.
- After upgrading the application, tool-tips are not displayed for email message and in-person signing fields for templates.
- The Q&A authentication type is not auto-populated when a package is created from a template.
- Salesforce users can not opt-out of a package if they access the package through their Salesforce account. However, they can opt-out of the package if they access it through the email link.
- On Internet Explorer, an error message is displayed when attempting to drag-and-drop files within the Select Documents from Salesforce dialog box.
- On Internet Explorer 9 and 10, documents cannot be added from the local drive to packages or templates.
- If in a previous installation the OneSpan Sign Configuration Name has been changed from the Default name, after upgrading, the Salesforce admin must manually add
profile=salesforceto the Canvas App Url Parameter. If this value is not populated, a Send button appears instead of the instruction banner in the designer page.