OneSpan Sign Sign

This feature is not yet supported in the Lightning Experience DocGen Designer.

Note: OneSpan Sign was formerly known as eSignLive. For all information related to eSignLive refer to OneSpan Sign.

Send DocGen Package output to recipients for electronic signature with OneSpan Sign. You add an OneSpan Sign Delivery Option to the DocGen Package, then you create a list of recipients. With the recipients in place, you can tag your templates for signatures. After you create the delivery, add your recipients and update and add a template to Salesforce, you are ready to run the DocGen Package.

You can integrate OneSpan Sign with Nintex DocGen to deliver documents for an electronic signature. You collect some information about your OneSpan Sign account, then set up the OneSpan Sign integration in the NintexDocGen for Salesforce app.

Integrate a OneSpan Sign account with Nintex DocGen

OneSpan Sign account requirements

The app will not deliver output files if the Salesforce user running the delivery does not have an OneSpan Sign account that meets all the following requirements.

  • Salesforce email of the user generating documents matches an OneSpan Sign Sender account.

  • OneSpan Sign Sender account hasn't been locked by OneSpan Sign manager.

  • OneSpan Sign Sender account has been confirmed and configured (OneSpan Sign has an invite state for accounts, but it isn't fully operational until confirmed and configured).

Get the OneSpan Sign Base URL

You need the Base URL for OneSpan Sign to integrate with Nintex Drawloop DocGen® for Salesforce. This value depends on the geographic location of your OneSpan Sign account and, in the US, the interface you're using.

Log on to the OneSpan Sign site. For Base URL, use only the first part of the URL (everything between the protocol and the top level domain) on the logon page.

Note: You can also get the value for Base URL from the OneSpan Sign for Salesforce app. if you have the app installed. In the OneSpan Sign for Salesforce app, you must select an environment, which provides you with a Website URL. Use this value for Base URL.

Get the OneSpan Sign API Key

Your OneSpan Sign API Key (and how you get it) is different based on whether you're using an OneSpan Sign production or sandbox account.

  • If you have an OneSpan Sign production account, you must contact OneSpan Sign support to get your API Key.

  • If you have an OneSpan Sign sandbox account, you can find the API Key on the OneSpan Sign web site. Sign into your account, go to the Integration section of Admin, and the API Key appears obfuscated at the top of the page. Click the eye icon to reveal your API Key.

Third-party OneSpan Sign integration

With the Base URL and API Key, you're ready to integrate OneSpan Sign with Nintex DocGen.

Integrate OneSpan Sign with Nintex DocGen

  1. From the Force.com app menu, select Nintex DocGen, and then click DocGen Admin.

  2. Under Configuration, click Third-party Integrations.

  3. From Add Service, select OneSpan Sign.

  4. Enter the API Key and Base URL and click Save.

Add an OneSpan Sign delivery option

You can add an OneSpan Sign Delivery from the DocGen Package Wizard or the Delivery Options related list on a DocGen Package. The wizard offers access to common options for all deliveries, but you must finish configuration from the related list, where you can set up recipients.

  1. From the Force.com app menu, select Nintex DocGen, and then click DocGen Packages.

  2. Select New.

  3. From Basics, enter required information in these fields:

    1. DocGen Package Name

    2. Type

    3. DocGen Package Starting Object.

  4. From Delivery Options, in Type, select OneSpan Sign.

  5. In Name, type a name (that the user running the DocGen Package will see) and then configure any remaining fields for standard options.

  6. Select a Document Output Type:

    • PDF: This output type will return a single PDF consisting of all of your documents.

    • Originals: Do not select this option for OneSpan Sign.

    • Separate PDFs: This output type will return a single PDF for each template within your DocGen Package, regardless of format.

      You must add a signing tag to each output document.

    • PDF and Originals - Do not select this option for OneSpan Sign

  7. On DocGen Package Templates, select or upload a template and click Save.

  1. From the Force.com app menu, select Nintex DocGen, and then click DocGen Packages.

  2. Select a DocGen Package you want to add or edit a OneSpan Sign Delivery option, and take one of the following actions on the Delivery Option related list.

  3. Click New Delivery Option, from Type of new record, select OneSpan Signand then click Continue.

  4. From an existing OneSpan Sign Delivery, click Edit.

  5. In Name, type a name (that the user running the DocGen Package will see) and then configure any remaining fields for standard options.

  6. (Optional) In Redirect URL, type a URL to redirect third party process.

  7. Select a Document Output Type:

    • PDF: This output type will return a single PDF consisting of all of your documents.

    • Originals: Do not select this option for OneSpan Sign.

    • Separate PDFs: This output type will return a single PDF for each template within your DocGen Package, regardless of format.

      Tip: You must add a signing tag to each output document.

    • PDF and Originals: Do not select this option for OneSpan Sign

  8. (Optional) Select Allow Subject and Email Changes.

  9. Allow Subject and Email Changes - Selecting this checkbox will allow the user who runs the DocGen Package to make changes to the subject and body of the email message at run time.

  10. (Optional) In Email Text type text to display in the body of the email.

  11. (Optional) Allow Remind and Expire Changes: Checking this box will allow Salesforce users to change defaulted values in the fields located within the Remind and Expire section of the Edit Page

  12. (Optional) Reminder Delay: Entering a number here will delay the time in which your first reminder is sent in units of days.

  13. (Optional) Reminder Frequency: Entering a number here will determine the frequency in units of days for which additional reminders are sent to recipients.

  14. (Optional) Days till Signing Expires: This field determines the number of days allowed for eSignature until it expires.

  15. Click Save.

Add or edit recipients for an OneSpan Sign delivery option

After you add an OneSpan Sign Delivery, you must add recipients to sign the output documents. For example, if you needed a client and a representative from your company to sign a contract, then your delivery option would require two recipients.

To add a recipient to an OneSpan Sign Delivery

  1. From a DocGen Package that has an OneSpan Sign Delivery, on the Delivery Options related list, click Name for the delivery option.

  2. In Recipients, click New Recipient to add a recipient or click Edit to edit an existing recipient.

  3. In Recipient #, type a number.

    1. Recipient # - Enter a number here for your recipient. Best-practice is to make this the same number entered into the Signing Order field. This number will be appended to the field tags for the recipient.

  4. In Signing Order, type a number.

    1. Signing Order - The numbers entered here determine the order of your recipients if you have multiple recipients. For example, a value of three means that the recipient will be the third person to receive the document for signing.

  5. In Sign Options, select the options you want and click Add.

    1. Sign Options - If you plan to use the standard sign options provided by the electronic signing service, you must add those options to Chosen Sign Options. This will add field tags to the DocGen Package Field Tagger for the recipient being created.

    OneSpan Sign Recipients require at least one Sign Option.

  6. In Role Name, type a name.

    1. Role Name - Enter the role name for the recipient here. This will be visible to the Salesforce users on the run DocGen Package page

  7. Select Required.

    1. Required - Clear this checkbox to make a signature from this recipient optional for the user generating documents. If you select this checkbox, the user generating documents will have to send the documents to this signer for a signature.

  8. Clear or select Display Title.

    1. Display Title - Selecting this option will display the recipient's title on the run DocGen Package page.

  9. In Embedded Signer, select an option.

  10. You can make the first recipient an embedded signer by selecting Routed via LOOPlus in this field. Embedded signers can provide their signature by signing within Salesforce immediately after the document is sent for signature. You can set only one recipient (the first) as an embedded signer at this time.

  11. In Specified Signer, select an option to identify this signer.

  12. Click Save.

Tag Templates for OneSpan Sign

In order to fully utilize the OneSpan Sign delivery method you must tag templates for OneSpan Sign delivery. You set up the OneSpan Sign Delivery with at least one recipient, then add OneSpan Sign tags to your templates wherever OneSpan Sign signatures should appear.

Tag a OneSpan Sign template

  1. From the Force.com app menu, select Nintex DocGen, and then click DocGen Packages.

  2. Select a DocGen Package with an OneSpan Sign delivery that has at least one recipient and click Field Tagger.

  3. In Field Tagger, from Main Object, select Recipients.

  4. From Recipient, select the Recipient that corresponds to the recipient from the OneSpan Sign Delivery.

    Fields defined for the selected Recipient appear in Field Tagger.

  5. From Field Tags, copy the value from Tag and add it to your document.

Note: After you tag your templates, change the font color of the tags to match the background of your document. This makes the tag invisible in the PDF output document, but allows the signing service to tag the documents.

Send output documents to OneSpan Sign for signature

After you add the OneSpan Sign delivery and a recipient to your DocGen Package, you can deliver documents to OneSpan Sign for signature.

To send output documents to OneSpan Sign

  1. Select a DocGen Package with an OneSpan Sign Delivery Option with at least one recipient.

  2. Click Select Record and then select a record, a contact and then the OneSpan Sign Delivery. For more information, see DocGen Package object testing.

  3. Select a signer.

  4. Click Run DocGen Package.

    Output files are generated. If you click the document, you can download it.

  5. Click Send to OneSpan Sign.