You are here: eSignLive Documentation > Release Notes > eSignLive 10/11 Release Notes

Release Notes for eSignLive 10/11

The following sections contain Release Notes for 11.* and 10.* versions of eSignLive:

Releases 11.x

This section describes:

Release 11.8 (Coming 6-9 November 2017)

What's New

  • Enabled the User Interface to automatically extract signatures and fields by placing Text Tags directly in a document. Previously, this feature was available only to integrators (see Release 11.5).
  • Completed all preparations for disabling TLS 1.0. For the associated schedule and expected impacts, click here.
  • Extended Personal Certificate Signing to all supported browsers on Microsoft Windows.

Bug Fixes

  • PB-4372: Enabled the graceful handling of an interruption of Internet connectivity during the Signing Ceremony.

Release 11.7

What's New

  • Enabled the Apple Pencil to be used in the Signing Ceremony.
  • Prevented signers from downloading documents until they have accepted the eSign Consent form.
  • Enabled the Callback timeout to be configured to give the Callback endpoint extra time to process a Callback request.

Bug Fixes

  • PB-3919: Fixed an issue that had been causing delays when users were searching for layouts.

Release 11.6

What's New

  • PB-3366: Improved the "quicker access" feature implemented in Release 11.4, so the Signing Ceremony launches only when the transaction is awaiting your signature.

Bug Fixes

  • PB-3320: Fixed an issue that had caused a transaction's status to remain Active, even though all signers had completed signing.
  • PB-3026: Stopped an additional placeholder recipient from being added to a transaction when a layout is applied.
  • PB-2151: Corrected Dutch and Portuguese labels and translation errors.

Release 11.5

What's New

  • Added the ability to automatically extract signatures and fields by placing Text Tags directly in a document. eSignLive will analyze the uploaded document, and replace every text that matches the Text Tag pattern with the appropriate signature or field. For more, see Text Tag Extraction. Note: This feature is currently available only to integrators.
  • Enhanced the SMS Phone Number field to use the country code of the transaction owner as the default country code.
  • As soon as a sender completes signing a transaction, they are now prompted to proceed to the next transaction.
  • For security reasons, we removed support for Internet Explorer 8 . We also recommend no longer using IE 9, IE 10 or Windows 8, since Microsoft has ended its support and security updates for those products.

Bug Fixes

  • PB-3259: Fixed the Mobile Signing Ceremony to enable styling of the Thank You page.
  • PB-2590: Made the Date format for extracted fields follow the Date format for Custom Accounts.
  • PB-3304: Removed the Resend SMS action for archived transactions.
  • PB-1402: Ensured that a transaction's creation date is returned (instead of its sent date) when active transactions are retrieved.
  • PB-1164: Prevented double-clicking on the Handover action. Double-clicking had been causing a second unnecessary call to the customer's page.

Release 11.4

What's New

  • Implemented quicker access to the Signing Ceremony. The application will determine if it is your turn to sign. If so, it automatically launches the Signing Ceremony when you click on a transaction from your Inbox. This applies to all transactions awaiting your signature.

Bug Fixes

  • PB-1889: Displays an appropriate error message when an expired transaction is returned to the status of Draft. Once in Draft, the transaction owner can extend the expiry period, and re-send the transaction for signing.

  • PB-1671: Fixed an error that had been causing messages to overflow outside an iPad's visible area. This had been causing an expiry message to overlap with the page border.

  • PB-1660: Fixed the mobile Signing Ceremony's title bar. If the document name was too long, it overlapped with the expandable-menu icon.

Release 11.3

What's New

  • Remodelled the Add/Edit Recipient dialog box that appears in the Sender Interface by converting its top horizontal tabs into vertical sections on the left. This enabled: (1) the addition of extra settings; (2) better support for mobile devices that have limited horizontal space. For a description of the new interface, see Recipients.
  • Extended Personal Certificate signing to external signers. Formerly, such signing was available only to holders of an eSignLive Account.
  • Removed the Expiry Warning dialog box to ensure consistent behavior across all supported browsers, desktops, and mobile devices.
  • Extended label customization to the Guest Authentication page. The message that will appear on that page is now fully configurable at the account level.
  • Created a new DIGIPASS Signing feature that enables the use of VASCO DIGIPASS Authenticators to validate the identity of signers, and to authorize the approval of each document in a transaction. When a signer is added to an eSignLive transaction, DIGIPASS may be specified as the two-factor Authentication Method. For more on how to leverage this feature, please consult your Sales or Customer Success representative.
  • Added automatic email blacklisting. For details, see the warning box in the procedure Adding Recipients.

Bug Fixes

  • PB-1348: Corrected the French message that appears when senders are invited to join an account.
  • PB-1396: Enabled a sender to add an unlimited number of delegates who can operate on their behalf.
  • PB-1294: Enabled the deletion of partially signed documents.
  • PB-1544: Ensured that the SMS Guest Authentication page respects the signer 's language.
  • PB-1759: Ensured that only one SMS code is sent to a signer when both SMS Authentication and KBA Authentication are used.

Release 11.2

What's New

Integration
  • Enhanced the Integration Model to include the transaction creation date (in addition to the completion date and date of the last update). This enhancement applies to both the API and the SDKs.
  • Enhanced the Event Notification payload to include the event timestamp. This timestamp specifies the time of event creation to within a millisecond. For more information, click here.

NOTE:  By default, eSignLive's SDKs ignore additional fields. To take advantage of the new fields described above, upgrade to the 11.2 SDK.

WARNING: If you are using the API directly, you must ensure that your integration code can ignore new fields. Otherwise, your integration will no longer work.

Other
  • Added customization support to the New User Interface's login page for on-premises and private-cloud deployments. This enables the footer, sign-up link, and What's new link to be hidden on the login page. The login page for the Classic User Interface already provides this level of customization.

  • Removed all references to eSignLive™ and eSignPackage™ from Signing Ceremony labels in order to extend white-labeling capabilities.

  • Increased the size of the mobile Signing Ceremony's Reason field for opting out and declining in order to support longer text.

Bug Fixes

  • PB-489: Ensured that all Signing Ceremony errors are displayed in the signer's specified language across all browsers (including when the session expires, or when the transaction is no longer active).
  • PB-766: Corrected French labels and translation errors. These corrections apply to labels in both desktop and mobile Signing Ceremonies.

  • PB-472: Fixed an issue that had caused the URL to be double-encoded when the Signing Ceremony is viewed in Chrome. This issue affected only on-premises deployments that were trying to connect through a proxy.

  • PB-236: Fixed the border of the Notary Seal when an eNotary transaction is created from the New User Interface.

  • PB-935: Preserved the Document Delivery option when a transaction is created from a template with group signers.

  • PB-862: Fixed a bug that caused the Session Extend dialog box to appear after the relevant session had expired.

Release 11.1

What's New

  • Extended the Document Visibility feature to enable senders to use the Designer to configure the visibility of documents to recipients.
  • Enabled the styling of text in the Thank You dialog box and on error pages.
  • Enabled signers to request a new SMS code.
  • Added a prompt for the sender to start signing immediately after sending a transaction.

Bug Fixes

  • PB-260: Removed the latency that had been occurring when a large number of layouts was loaded via the Designer.
  • PB-638: Removed a white border that had appeared around PDF fields during the execution of field injection.

Release 11.0.6

What's New

  • Created a new signature-capture feature at the transaction level. If this feature is enabled, signers must capture their signature every time they sign. Otherwise, the signature is captured only once, and then applied to all subsequent signatures, for which the signer clicks to sign.
  • Created a Download All button for signers. Clicking it downloads a zip file that contains all signed documents associated with a completed transaction.

  • Can now customize a large set of labels for the Signing Ceremony and for error pages. An example of an affected error page is the Access Denied page that appears when a transaction is no longer active.
  • Added a Decline option to the Signing Ceremony on mobile devices.

Bug Fixes

  • APP-5523: In eSignLive for Box, the name of a signed file returned to Box had been truncated. Now that name contains as a prefix the original name of the unsigned file.

Release 11.0.5

What's New

  • Created a Document Visibility feature that enables integrators to control which recipients can view specific documents in a transaction during a Signing Ceremony. This saves recipients from having to process documents they don’t need to see, and it ensures that documents with sensitive information are viewed only by their intended recipients.
  • Created an Event Notifier plug-in. If the Signing Ceremony is hosted in an iFrame, the Notifier can send events from the Signing Ceremony to the parent hosting application. This is useful if the integrator wants to be notified when certain steps take place during signing. Upon receiving such notifications, the integrator can perform actions to enhance the User Experience, display supporting messages, or update visual components in the hosting application.

  • Enabled the branding of all data in Evidence Summary documents. Formerly one could only customize the logo for those documents, but now in addition the logo can be hidden, the title can be customized or hidden, other sections can be selectively hidden, all labels for each field can be customized, etc.
  • Enhanced SMS security by making the SMS code single-use. A new code is now sent every time the signer clicks the email link, instead of only when the transaction is initially sent.

Bug Fixes

  • An error message now appears if a user tries to update an attachment for a package that has been completed by the Package Owner.

Known Issues

  • The enhanced SMS security feature described above has a known issue. If you are using Email Protection Software (e.g., proofpoint), you may receive two SMS messages instead of one. The first arrives when you click the link in your email invitation. The second arrives when you enter the SMS code to access the Signing Ceremony. Although inconvenient, the second SMS message is harmless.

Release 11.0.4

Bug Fixes

  • Stopped the entire page from being dragged when a user tries to drag a Signature Block across the page.
  • Ensured that inactive sessions are redirected to the pre-configured URL in the Classic User Interface.

Known Issues

  • A user's specified language — French — is not respected in the following situation. (1) A French transaction is emailed to a third-party recipient with Question-Answer authentication. (2) The recipient clicks the email link, and a guest login page appears in French. (3) The recipient inputs incorrect answers to questions until the recipient is locked out, and an error message appears in French. (4) In the same browser, the recipient clicks the email link again. An error page appears in French. The system has behaved well to this point. (5) The recipient opens a new browser (with clean cache & cookies), and opens the email link again. The error message that appears is now in English.

Release 11.0.3

What's New

  • Added a Date field that enables a signer to specify a date from a calendar.

  • Extended the Group functionality to all Account senders.

  • Added sender pagination and search capabilities to the eSignLive BackOffice administration tool.

Bug Fixes

  • Fixed the iFrame Signing Ceremony on iOS Safari.

  • Made the mobile Signing Ceremony redirect to the desktop Signing Ceremony if CAC/PIV Certificate Signing is detected.

  • Fixed sorting on the Account > Senders page.

  • Fixed the Salesforce banner when signing occurs within Salesforce.

  • Fixed footer placement for signing on an iPad.

  • Fixed the adding of attachments in the Firefox v49 browser.

  • Formerly, after clicking an Invitation Email's link, and then logging into eSignLive, signers were directed to their own Inbox. Now they are immediately directed to the Package page for the package they've been invited to sign.

Release 11.0.2

Bug Fixes

  • Fixed the alignment of "e-Signed By ..." text in signatures when the text is smaller than the Signature Block.

  • Fixed Session Expiry auto-redirect to a Custom URL.

Release 11.0.1

Bug Fixes

  • Upgraded Google Guava from 15.0 to 17.0.
  • Changed many references in the code from e-SignLive (with a hyphen) to eSignLive (no hyphen).
  • Added a new feature that configures a signer's Authentication Token to be single-use only.
  • The uploadDocument method wasn't properly refreshing the Package Object. We therefore deprecated the old uploadDocument method, and added a new uploadDocument method that uses the Package ID instead of the Package Object.
  • Previous releases used the Fast Track URL Mapper with the location header. Instead, 11.0.1 uses the currently requested URL if no Redirect is specified.

Release 11.0

What's New

  • New UX/UI: We've introduced a redesigned GUI and User Experience that: (1) focus on preparing and managing transactions; (2) emphasize ease-of-use and visual clarity. For more, see the New Application User's Guide.
  • Personal Digital Certificate: This feature enables a signer to sign documents with their own certificate. This feature can be leveraged by governments and other regulated agencies whose employees have their own certificates.
  • TEMPLATE_CREATE callback: This enables an account to receive a callback when a template is created from scratch, or when a template is saved from an existing transaction.
  • Danish Language Support: Signers and senders can now choose to view eSignLive in Danish. This support includes email templates, in that transaction owners can specify Danish as the language to be displayed to an individual signer.
  • Change Signer Authentication: Added the ability to specify SMS or Q&A authentication when the identity of a signer is being changed. This is especially useful if no individual was specified when an invitation was sent. For example, consider a transaction that sent an invitation to sales@acme.com. Upon receiving that invitation, Acme's Sales Team can: (1) change the signer to a particular person – e.g., joe@acme.com; (2) specify that Joe's phone number will receive an SMS authentication code.
  • Session Fields: Integration customers who want to store extra data as part of their signing evidence can pass additional session fields per signer when they create a signing session. These fields are saved in the Evidence Summary, and are stored in the signature details of signed documents. For example, an external system's Login Token can be stored as part of a signature's Audit Trail.

Other Changes

  • End-of-life for Package: The term Package has served us well for six years, but it's time to embrace a term that's becoming more common in the market. In this release, the term Package will be replaced by the term Transaction.
  • QRCodes: This feature has also reached its end-of-life. It will be deprecated in favour of the Evidence Summary, which offers more Audit Trails.

Bug Fixes

  • Fixed the duplicated Session Expiry warning when a signer's session expires.
  • Prevented an Administrator from deleting the Account Owner on the Senders page.
  • Ensured that when signed documents are sent as email attachments: (1) they are flattened; (2) the flag flattenSignedDocuments is on.
  • Fixed translation issues for non-English languages in the Delegation section.

SDK

What's New
  • Can now sign documents as the API key owner, or for another signer
  • Added RTF and ODT to the document type enum.
  • Improved error handling for Text Anchors.
  • Added a transaction signAll capability. This API/SDK call enables all documents in a transaction to be signed in one call (instead of traversing documents successively, and signing each signature successively).
Bug Fixes

The following issues were fixed:

  • Box connector 502 Bad Gateway error
  • Remove QRCodeTest from both SDKs
  • DocumentType enum in SDK only includes PDF and WORD document types
  • Accept header not set when getting AuthenticationToken

Releases 10.13.x

This section describes:

Release 10.13.17

What's New

  • Enabled the Apple Pencil to be used in the Signing Ceremony.
  • Security and performance enhancements.

Release 10.13.16

What's New

  • Updated the environment to enable the Canadian migration to version 11 of eSignLive.

Release 10.13.15

Bug Fixes

  • PB-260: Removed the latency that had been occurring when a large number of layouts was loaded via the Designer.

Release 10.13.14

What's New

  • Created an Event Notifier plug-in. If the Signing Ceremony is hosted in an iFrame, the Event Notifier can send events from the Signing Ceremony to the parent hosting application. This is useful if the integrator wants to be notified when certain steps take place during signing. Upon receiving such notifications, the integrator can perform actions to enhance the User Experience, display supporting messages, or update visual components in the hosting application.

Bug Fixes

  • An error now appears if a user tries to update an attachment for a package that has been completed by the package owner.
  • This fix concerns the system's behavior when a user clicks the Opt Out button on a mobile device. We ensured that the text field called "Other" no longer appears in the mobile transaction if that field has been disabled at the transaction level.

Release 10.13.11

Bug Fixes

  • Enhanced certain translation labels.
  • Ensured compatibility with Firefox 49.
  • Ensured that clicking an e-mail link redirects to the relevant transaction after a successful login.

SDK

What's New
  • Support for signature images
  • Bug fixes
  • Removed the .NET SDK dependency on log4net (for .NET only)

Release 10.13.10

What's New

  • Extended the ability to override the default text that appears during the Signing Ceremony.

  • Can specify the default settings of fields at the Account level.

  • Can specify at the Account level which fields senders can view when they are preparing a transaction.
  • The list of fields that appears during the Signing Ceremony now includes a Date field.
  • Made the Thank You dialog box appear on a package’s last document, instead of on the last document that contains signatures.

Bug Fixes

  • Fixed the scrolling and dragging operations that are used to capture signatures under IE 11.

  • Fixed the error that had occurred in a mobile Signing Ceremony when a user selects a checkbox after capturing their signature.

Release 10.13

What's New

  • Platform unification phase-1.
  • Application performance enhancements.
  • Add BBC capabilities to all email templates.

SDK

What's New
  • Support for signature images.
  • Bug fixes.
  • Removed the .NET SDK dependency on log4net.

Releases 10.10.x

This section describes:

Release 10.10.2

What's New

  • If group signing is turned on, do not send duplicate SMS messages to signers who are in multiple groups.
  • Allow disabling of activation emails for in-person packages.

Bug Fixes

  • Fixed the label text in the in-person affidavit page.
  • Fixed the signature capture on the identity page for iPad/iPhone.

Release 10.10.1

Bug Fixes

  • Ensure the custom account logo and package branding bar appear on the guest authentication, thank you dialog, and signing ceremony.

SDK

What's New
  • Added a function to trash and/or archive a package (Java only).
Bug Fixes
  • Support for Connectors callback.
  • Added a function to restore a package, and to mark a package as complete.
  • Exposed the name of the placeholder so that connectors can edit the placeholder name.
  • Fixed a bug to return the proper URL encoded filename.
  • Fixed a bug where the existing document was overwritten when adding a new document with the existing documents name. To do this, the document field type has been changed to a list.

Release 10.10

What's New

  • Bulk Send is a feature that gives users the ability to create multiple packages simultaneously using an existing template in conjunction with uploading a CSV file containing ll of the signers' information.
  • Label Fields extends our supported field types to include a label field that is stamped on to the PDF once it is sent. In the signing ceremony, the label field will be shown as non-editable text.
  • An enhancement to In-Person Signing that allows the package sender to see the Now Signing as a dropdown box within the signing ceremony document page.
  • Added support for customizing the logout URL.
  • Added support for customizing the signer or sender expiry URL.
  • Added branding options to hide the page footer and QR Code button.
  • Added a Privacy Notice to the footer section of eSignLive.

Bug Fixes

Fixed the following issues:

  • The attachments map has been converted into an ordered list so that the backend returns attachments in the same order as they were inserted.
  • Differentiated between required and optional attachments.
  • In the audit trail, if a form field has a specified field name, that name is displayed instead of the generic term FormField.
  • The Clear All button was not visible when a QR code was added to a document.
  • Fixed an issue where the QR code is displayed in the designer when qrCode=false in settings.features.
  • Fixed an incorrect JSON payload for the PACKAGE_ATTACHMENT notification.
  • Fixed an issue with SMTP authentication using empty username/password values.
  • When an opted-out or declined package is trashed, the opt-out/declined reasons are not displayed.

Application Changes

  • Signing is now performed using the Amazon/Softlayer NTP servers. This enhancement speeds up signing by 20%.
  • The default setting for hideCaptureText is false. This is only applicable if the account does not have this setting specified.
  • Applied Logjam security patch to all systems.
  • Upgraded the domain SSL certificate to SHA-2 for added security.

Integration Changes

  • Standardized the internal auto-generated ID size for role and signer to 36 characters. This does not affect integration customers setting this ID manually. The maximum allowed size is still unchanged at 64 characters long.

SDK

What's New

Added SDK support for the following:

  • Previously, attachments were pooled in a map in the SDK before sending them to the backend. This map has been converted into an ordered list so that the backend returns attachments in the same order as they were inserted.
  • Support to obtain an attachment's original filename.
  • Support for label fields.
  • Deprecated the method createPackageFromTemplate (DocumentPackage documentPackage PackageId packageId) in TemplateService.
  • Removed the functionality to lock a signer using the SDK.
  • Support for disableDeclineOther and disableOptOutOther settings in CeremonySetting.
  • To fix a bug where the existing signer disappears when adding a new signer with the existing signer's email address, the signer placeholder field type has been changed to a list.

Releases 10.9.x

This section describes:

Release 10.9.3

Bug Fixes

Fixed the following issues:

  • Duplicate email when uploading required attachments.
  • Fixed package creation from templates with placeholders.
  • Fixed in-person signing when the signer record is modified.
  • Fixed editing template settings.
  • Security enhancements.

Release 10.9.2

Bug Fixes

  • A message is displayed for users using the Mobile Signing Ceremony that cookie settings must be set to Always Allow for Safari, and Allow Third Party Cookies for Android browsers.
  • Minor security fixes.

Release 10.9.1

Bug Fixes

Fixed the following issues:

  • When document visibility is set to signer, the expected behaviour is that, when the package is completed, the signer can see all the documents.
  • Broken link error message if a signer is deleted.
  • Completion reports through the SDK would return nothing.
  • The groups tab is not visible for group managers.
  • The text in the customized thank you dialog box is not displayed correctly.
  • The configure signer buttons are not displayed correctly due to case mismatches in the email address.
  • The SharePoint connector cannot create a package from a template that contains a placeholder.

Release 10.9

What's New

  • Secure callback authorization key adds the ability to use Basic Authorization to make callback notifications more secure.
  • Added event notifications for when a package has attachments, and when a signers' account becomes locked.
  • Automatically email the electronic evidence summary and package documents to the package owner upon package completion.
  • Delegate access adds the ability to grant access privileges to other users in the same account.
  • Improved HTML link buttons within email templates, available for all eSignLive supported languages.
  • Improved mobile signing ceremony experience, including support for the following:
    • Added support for in-person signing and changing signers.
    • Customizable client branding experience on mobile devices.
    • Form fields are now fully supported.
    • Improved readability for long document titles.
    • Improved behaviour for devices with their screen rotation locked.

Releases 10.8.x

This section describes:

Release 10.8.6

Bug Fixes

Fixed the following issues:

  • The add signer button is not displayed correctly when opted-out and declined packages are edited.
  • Documents indicator displays an incorrect colour.
  • Incorrect navigation message when reviewing a document.
  • Signer workflow caused the number of signatures for the package owner to be displayed incorrectly.
  • An iFrame issue with eSignLive for Oracle Documaker has been fixed.

Release 10.8.5

Bug Fixes

Fixed the following issues:

  • Capture Signature not working correctly when applied to multiple documents.
  • Signers who have defined a handwritten signature on their identity page cannot sign documents with the capture signature type.

Release 10.8.4

Bug Fixes

Fixed the following issues:

  • In Internet Explorer 9, the "Thank you" dialog does not appear after an attachment is uploaded.
  • After completing the signing ceremony, the opt-out button is displayed.
  • When Do not auto-complete package and Define a workflow are selected, the message "Your signature is not required on this document" is incorrectly displayed.
  • When Do not auto-complete package is selected, the continue button in the document toolbar is not displayed.

Release 10.8.3

Bug Fixes

Fixed the following issues:

  • In Internet Explorer, the signing ceremony page and the view document page automatically scrolls to the document toolbar midway down the page.
  • Document Engine fix to handle different message sizes coming from the timestamp server.

Release 10.8.2

Bug Fixes

Fixed the following issues:

  • In some cases, certain signature blocks are unsignable when bot a group signature and an individual signature are present.
  • The account summary report was not functioning as expected.

Release 10.8.1_BE18

Bug Fixes

Fixed the following issues:

  • In very specific cases the document properties were incorrectly reporting that the document had been altered.
  • KBA: support for modifications made in the Equifax API.
  • Signature blocks are displayed on documents of trashed packages.
  • Cannot confirm signatures on documents when a signing order is enforced.

Release 10.8.1_BE17

Bug Fixes

Fixed the following issues:

  • An intermittent issue in which signers could not confirm signatures on documents.
  • PDFs with the NeedAppearances flag set to true are unsupported at this time. Documents of this type are detected earlier in the package creation process.
  • When using group signing, the incorrect signature block is displayed for some singers.

Release 10.8.1

What's New

How-to overlays: first time users of eSignLive will be shown graphical overlays that explain how to create, prepare and send a package in 3 easy steps.

Bug Fixes

Fixed the following issues:

  • The progress bar displays the incorrect count for the number of signatures.
  • The designer view does not load when adding a document from history.
  • The progress bar does not appear in the package view of an active package.
  • The default "Thank You" dialog is not displayed correctly.
  • Updated messages and translations for mobile devices.
  • Updated French translation for the authentication tab.

Known Issues

  • In Internet Explorer, the signing ceremony page and the view document page automatically scrolls to the document toolbar midway down the page.

Release 10.8

What's New

  • Group Signing: Support for Individual and group member role overlap.
  • More customization options: including customizable "Thank You" dialog boxes, error pages, and navigation bar messages.
  • Optimized signing experience on mobile devices.
  • Control over Q&A Default Masking options.
  • Email bounce back event notifications.

Bug Fixes

  • Session token of embedded Designer view can no longer be reused to open an Inbox session
  • Un-archive a package. Customers who had archived packages by accident had lost the ability to bring back archived packages to their inbox. The functionality has been restored.
  • On-going security reinforcement.

Release 10.7

What's New

  • Mobile Signature Capture: Use a mobile device to capture your signature. For more, see Mobile Documentation.
  • API requests must contain the following API version header to use this feature:
Accept: application/json; esl-api-version=10.7

Bug Fixes

Fixed the following issues:

  • KBA can now be configured to display only one KBA provider (Equifax Canada or Equifax USA) for an account.
  • Evidence Summary button now working correctly in package view.
  • Fixed an error that occurred when attempting to delete a template.
  • Fixed an issue where when a package is opted out or declined, the document view would not show the Send button for the Sender.
  • Fixed colour contrast issues for links in Warning messages.

Releases 10.6.x

This section describes:

Release 10.6.2

Bug Fixes

Fixed the following issues:

  • Signature locator is now working properly on iPhone 4 and 5.
  • Fixed an issue that prevented the Reports page from working.
  • Fixed a race condition that was causing intermittent behaviour with signature blocks.

Release 10.6.1

What's New

  • API Versioning: As of version 10.6, all API requests need to contain the following header parameter to take advantage of extended form fields:
  • Accept: application/json; esl-api-version=10.6
  • A "What's New!" link has been added to the eSignLive login page detailing all that is new in eSignLive.
  • Inbox filtering.
  • Appearance of error/warning/information/success messages is being changed to adopt a lighter colour palette.

Bug Fixes

Fixed the following issues:

  • A session time out error will only be displayed when a time out occurs while attempting to save data.
  • KBA access denied error page will show customized contact information if available.
  • KBA signer verification page will allow the removal of the eSignLive banner if configured.
  • Deprecated email notification configuration mechanism will be correctly enforced.

Release 10.6

What's New

  • e-Notary: Notarization is used in a wide variety of circumstances relating to the signing of documents, including: transfer of land and vehicles, insurance settlements, liens, trusts and many others. This release introduces the ability to e-notarize documents using a completely electronic process.
  • SAML: Support for the SAML protocol to facilitate integration with 3rd party software products that provide single sign-on authentication.
  • KBA: Knowledge-based authentication, or KBA, uses knowledge questions to verify an individual's identity. KBA questions are generated dynamically and based on information in a signer's Canada or USA Equifax credit report.
  • OFAC: The OFAC Blacklist feature, when enabled, can limit the use of eSignLive from within certain countries.
  • Additional form field types: lists, radio buttons, and text areas.
  • Miscellaneous UI enhancements. For more, see the Classic Application User's Guide.

Bug Fixes

Fixed the following issues:

  • Fixed an issue where the custom account logo would not display in the package view.
  • Opt-Out and Decline now properly redirects to package/inbox.
  • The package due date field is now validated and does not let you update or create a package/template with an expired due date.
  • The footer of the Guest (SMS/Q&A) page now respects the layout.footer package settings.
  • In Internet Explorer 8, fixed an issue where the language dropdown menu would be transparent.

Release 10.5.1

What's New

  • Extended configuration options for the Designer View: The Designer View is now configurable, allowing for many of the designer elements to be hidden.
  • A new API route to send SMS notifications even when email notification is turned off.

Bug Fixes

Fixed the following issues:

  • When creating a package from a template with an expiry date, the expiry date would be copied over to the new package.
  • Users were sometimes unable to create a package with an expiry date of "tomorrow".
  • Updating the account owner's identity for Title and Company would not use the new values in the signing ceremony.
  • User would receive duplicate emails if a package was declined.
  • Security fix: As a signer on package, it was possible to change any role within a package.