Using Signatures

Placing a signature block is as simple a placing it on the form. The signature block must then be configured with its signers details. Signer details are provided through field references available on the E-Signature widget. Date Stamps can be placed in the same way as E-Signatures and are configured by linking the signature they will display the timestamp for.

NOTE : Currently E-Signatures may only have a single date stamp.

Positioning Signatures & Date Stamps

Positioning the Signature & Date Stamp widgets can be done one of two ways :

1. Relative

   The block will be placed onto the pdf receipt where the tab was placed onto the form

2. Absolute

   The block will be placed onto the pdf receipt at the pixel location of the page number specified by the parameters "Page Number", "Position X" and "Position Y"

Embedding the signing ceremony

The embedded signing ceremony required minimal configuration, and can simply be placed on the form. The following rules are provided on the form to allow customisation of the signing experience :

1. On Complete

   Allows the form designer to specify a script to run when the signing ceremony has been completed.

2. On Failure

   Allows the form designer to specify a script to run if the signing ceremony fails (usually due to a signer opting out or declining to sign)

NOTE : The signing ceremony will begin as soon as the signing ceremony is visible

WARNING : Once the Signing Ceremony has been created it cannot be changed, as changing the contents of the documents would void the signing package.

Using an alternative document for signing

By default, the document presented to a user for signing will be the submission receipt PDF generated by Transact Manager. Sometimes however a document other than the submission receipt is required to be signed, such as a pre-defined contract document. The EsignLive - Create Package service can be configured to retrieve a PDF document from another location, to be used in place of the receipt PDF. The Document Service Name service parameter can be set to any Fluent Groovy service that will return a byte array containing a PDF document. The service must include the following method signature:

byte[] invoke(SvcDef svcDef, HttpServletRequest request, User user, Map params) {...}

For example, a Fluent Groovy service may be written that returns a previously uploaded document from an Organisation (or Form) property in Transact Manager. Alternatively, a 3rd party REST API may be utilised to provide a custom PDF containing data from the submission XML.

Delivering the Signed Documents

The EsignLive - Delivery Process is provided so completed eSignLive Packages will be attached to their respective transactions once all signers have completed their signing. The delivery process may be customised by configuring this service to call another delivery service once it has finished see the service help documentation for details.

Licensing

Clients must ensure they are appropriately licenses in order to use this package. Organisations who wish to use this package are required to establish a commercial relationship with eSignLive directly.

Compatibility

This package has the following compatibility requirements:

Release Notes

Version 1.2 January 28, 2026

• Implemented OAuth 2.0 authentication

  Updating to this version is mandatory, and requires following these steps:

  • Login to the OneSpan Sign dashboard with account admin credentials and:
  • Select "API Access" from the "Admin" dropdown
  • Select "OAuth 2.0 Client Credentials" radio button
  • Click OAuth 2.0 in the left nav panel
  • Click the +ADD link to add a new OAuth 2.0 Client
  • Add the new client and save the Client Id and Client Secret values
  • Edit the eSignLive Service Connection in JM and:
  • Enter the saved Client Id and Client Secret values into the Username and Password fields respectively

Version 1.1 Sep 05, 2019

• Fix JavaScript errors on ceremony page.
• Fix error handling for create package.
• Fix create package unit test.

Version 1.0 January 09, 2017

• Fluent SDK 5.1.0 update, documentation updates, resolved type-check error using groovy with closure

Installation Instructions

To install this package please walk through the following proceedure:

1. Unzip the package to a directory on your computer
2. Import each zip archive found in the services folder to Transact Manager under the Services >> All Services menu item.
3. Review the Help Doc tab for each of the imported services and make any required adjustments to service parameters.
4. Review the Service Connection requirements under the same Help Doc tab for each of the imported services and make any required configurations to the Service Connection. Service Connections can be configured in Transact Manager under the Services >> Service Connections menu item.
5. Import each archive found in the libraries folder to Maestro. Importing these into the Organisation level libraries folder is recommended as this will make the components available to all projects, however they can be imported at the Project level if required.
6. Also follow additional setup instructions in Release Notes

Release Notes