▲ Top

eSignLive for Microsoft Dynamics CRM: Release Notes

This document describes the following releases of eSignLive for Microsoft Dynamics CRM:

Release v2.1

What's New

  • Added support for TLS 1.1 and 1.2 at the level of the eSignLive for Microsoft Dynamics CRM server. This enables eSignLive for Microsoft Dynamics CRM to communicate with our API using the TLS 1.1 and 1.2 protocols. To learn about the status of TLS 1.0, see Dropping Support for TLS 1.0.

Bug Fixes

  • MAIN-2109: In certain situations, users were unable to enter information in a Text field. This issue has been fixed.
  • MAIN-2283: When Conventions were used to place signatures in a eSignLive for Microsoft Dynamics CRM document, identical signature ID numbers were created for all approvals. This meant that once the first approval was accepted, all other approvals were marked as accepted. This undesirable behaviour has been fixed.

Upgrading to Release v2.1 on eSignLive for Microsoft Dynamics CRM 2016

To update your solution to Release v2.1:

  1. By doing the following, ensure that the OneSpan Sign Notification Service is running, and that it has processed all notifications:
    1. On the eSignLive for Microsoft Dynamics CRM Server, log in into SQL Server Management Studio.
    2. From the Object Explorer, expand the databases.
    3. Right-click the database that was created during the SQL installation (for example, esignlive).
    4. Execute the following query:
    5. select * from EslNotifications where Processed is null
      1. If the Processed column contains NULL, you must wait until: (1) all entries are processed and updated to 1 by the Windows service; (2) there are no further entries.
      2. Run the above query again. The absence of rows will indicate that all rows have been processed.
  2. Stop the OneSpan Sign Notification Service by clicking Start > Administrative Tools > Services.
  3. Import the new eSignLive for Microsoft Dynamics CRM solution as follows:
    1. Log in to eSignLive for Microsoft Dynamics CRM as a user with Administrator privileges.
    2. From the top menu, select Settings > Solutions.
    3. From the Solutions grid, click Import. You are prompted for the location of the solution package.
    4. Click Browse, and select the provided solution package (e.g., ESLConnector_1_0_0_X_managed.zip).
  4. Click Next to display information about the new solution. eSignLive for Microsoft Dynamics CRM indicates that there is an update for your currently installed solution.
  5. Ensure that: (i) the option Maintain customizations (recommended) is enabled; (ii) you have checked any SDK message-processing steps that were included in the solution.
  6. Click Next. The solution is imported, and a summary page appears. A warning message may appear that can safely be ignored. The message states that when the solution was imported, the SDK message steps were disabled and then enabled.
  7. Click Close.
  8. From All Solutions, click Publish All Customizations. This ensures that eSignLive for Microsoft Dynamics CRMonline will be aware of all data changes that affect the User Interface.
  9. Reload the page. You should see that the solution is now the updated version.
  10. Restart the OneSpan Sign Notification Service by clicking Start > Administrative Tools > Services.

Release v2.0

Note that:

  • eSignLive for Microsoft Dynamics CRM v2.0 can be installed on eSignLive for Microsoft Dynamics CRM / 365 (8.1 or 8.2 ) online or on-premises.
  • eSignLive for Microsoft Dynamics CRM v2.0 requires OneSpan Sign version 11.0.4 or higher.
  • An instance of eSignLive for Microsoft Dynamics CRM can connect only to a single OneSpan Sign account, and vice versa.

What's New

With Release v2.0, users can:

  • Customize Dynamics CRM to display OneSpan Sign Packages within standard or custom entities
  • Populate signers' information with Dynamics CRM Leads, Contacts, or Users
  • Create and send OneSpan Sign Packages with Dynamics CRM documents
  • Auto-prepare OneSpan Sign Packages with text-tag Conventions
  • Use field-mapping Conventions to populate document fields with data from Dynamics CRM fields
  • Develop Dynamics CRM custom buttons to create and send OneSpan Sign Packages with the click of a button

Known Issues

  • ESSP-2889: When the Review After Completion option is enabled, the transaction is not complete even after all signers have signed. To complete the transaction, the transaction owner (OneSpan Sign Sender) must log into the OneSpan Sign portal, and mark the transaction as complete.
  • ESSP-1658: English should remain as the language of the Signing Ceremony for a package sender , even if the Package Language is changed to French when the package is created. However, the language that the sender then sees is French.
  • ESSP-2308: If the In-Person Signing option is selected, an error message appears when the signer declines or opts out of the Signing Ceremony.
  • ESSP-2361: When preparing a package using a Convention with the QR Code field, an Unexpected Error message appears.
  • ESSP-2717: When replacing a Convention, a notification appears with options to Cancel or Continue with the replacement. If a user selects Cancel, the application replaces the Convention instead of disregarding the action.
  • ESSP-2723: An incorrect error message appears when auto-preparing a package using a Convention with a Text Anchor text tag if the matching text is not found in the document.
  • ESSP-2742: When preparing a template with a Convention, the fields are not auto-populated. Therefore, auto-prepare does not work for the templates option.

Release v1.2

What's New

  • Added support for TLS 1.1 and 1.2 at the level of the eSignLive for Microsoft Dynamics CRM server. This enables eSignLive for Microsoft Dynamics CRM to communicate with our API using the TLS 1.1 and 1.2 protocols. To learn about the status of TLS 1.0, see Dropping Support for TLS 1.0.

Upgrading to Release v1.2 on eSignLive for Microsoft Dynamics CRM 2013 and 2015

To update your solution to Release v2.1:

  1. Log into eSignLive for Microsoft Dynamics CRM as a user with Administrator privileges.
  2. Navigate to eSignLive for Microsoft Dynamics CRM > Settings.
  3. In the Customization group, click Solutions.
  4. In the All Solutions window, click Import.
  5. You are prompted for the location of the solution package.

  6. Click Browse, and select the file Download eSignLive for Microsoft Dynamics CRM v1.2 Release Candidate (Solution Package).
  7. Click Next to display the Solution Information.
  8. Click Next to display the Import Options.
  9. Select the check box under Post Import Actions, then click Import. The solution is imported, and a summary page appears. After a certain delay, a message should state that the import was successful.
  10. Click Close.
  11. Click Publish All Customizations. This ensures that eSignLive for Microsoft Dynamics CRM online will be aware of all data changes that affect the User Interface.
  12. Reload the page. You should see that the solution reflects the version to which you've updated.

Release v1.1

What's New

  • Support for eSignLive for Microsoft Dynamics CRM 2015 on-premises.
  • UX Improvements:
    • Improved error message dialogs.
    • The double scroll bar was removed. Users can now control Designer and Signing Ceremony iFrame movements using a single scroll bar.
    • The Designer and Signing Ceremony iFrames are now more responsive, and re-size properly when pages are re-sized. The OneSpan Sign Designer Toolbar remains visible when users scroll down documents in the iFrame.
    • Sending packages is now done synchronously, and the package status is updated in real time . This enables users to start signing right after sending a package. The Send button has been removed from the Designer iFrame, and placed in the toolbar.
    • Moved the Send button from the embedded designer to in the connector.
    • Improved the experience of uploading documents by removing the step that required users to enter a document name (the filename is now used to initially auto-populate that field).
  • Enhancements
    • Users can now save the fields' layout (including all signatures fields) after they are placed on documents through the Save Layout feature available in the Designer iFrame toolbar.
    • Users can now apply a previously saved layout to the current document through the Apply Layout feature available in the Designer iFrame toolbar.
    • Users creating packages from templates with placeholders can now replace the placeholder with a signer without having to re-enter the Form Fields associated with the placeholder or signer.
  • Migrating from eSignLive for Microsoft Dynamics CRM 2011 to 2013 and 2015 has no impact on existing OneSpan Sign for Dynamics data.
  • Support for US and Canadian instances of OneSpan Sign.

Bug Fixes

  • By default, the In Person Signing Package setting is unchecked. However, users can override the default setting when they create new packages or templates. When creating packages from templates, the package settings are inherited from the template settings.
  • The order in which documents are uploaded to a template is now maintained.
  • Previously, when selecting the In Person Signing check box, signers were not presented with a drop-down list of all signers' names. The In Person Signing feature now appears to the signer with a drop-down list with the names of all signers.
  • Previously, it was not possible to create packages with the same name. This issue has been fixed, and users can now create packages with the same name.
  • Previously, users were not able to activate templates with no documents. This issue has been fixed, and users now can create and activate templates with no documents. However, when a package is created from a template. to prepare and send that package, a document must be attached.
  • Previously, packages with Enforce Signer Order unchecked allowed signers to be reordered. This issue has been fixed, so signer order is now maintained when this feature is used.
  • Previously, the First Name and Last Name fields had excessive size limitations. Now both accept up to 120 characters.
  • Previously, the Placeholder Name field had an excessive size limitation. It now accepts up to 100 characters.