Nintex eSign Delivery Option

The Nintex eSign delivery method enables you to send generated documents to one or many recipients while requesting an eSignature. This topic explains how to configure and use the Nintex eSign delivery option for Nintex DocGen. See Delivery Options to learn more about other options.

If a Nintex eSign delivery Option was created prior to version 18.2, then you will need to re-sync the Templates on the eSign Delivery Option to use the new DocGen eSign Envelope (see Nintex eSign Envelopes). If the Templates are not re-synced, the Nintex eSign Delivery Option will continue to create records for the Envelope Object from the eSign Lightning Application.

To use the Nintex eSign Delivery Option, the current Salesforce user must be an existing user within Nintex eSign.

Before you start 

Add Nintex eSign as an integration

After you have downloaded and configured Nintex eSign Lightning, you'll need to add Nintex eSign as an integration in Nintex DocGen. Follow the steps below, or use the DocGen Setup Wizard located in the Nintex Admin tab to perform the integration.

  1. Select the Nintex Admin tab.
  2. Under Configuration, select Integrations.

  3. To authorize Nintex DocGen for integrations, click the Authorize Nintex DocGen button. A new window opens and asks you to allow access. Click Allow. If you have configured this elsewhere in Nintex DocGen for Salesforce, then these options will not display.
  4. Under the Add Service drop down, select eSign.
  5. Select or enter the following fields:
    1. eSign Identity Provider - The region and URL that you use to log into eSign (e.g. https://account.assuresign.net).
    2. Nintex eSign Username - The Nintex eSign Admin's username that is used to log into Nintex eSign.

      Administrators can configure which Nintex eSign user is used for sending envelopes. To configure a Nintex eSign user for this task, go to Setup > Custom Settings > eSign User Settings > Manage. Then, set the Nintex eSign Context User at the Default Organization Level Value, Profile, or User level.

    3. Nintex eSign Password - The password associated to the Nintex eSign Admin's username.
  6. Click Authorize.
  7. If you have separate environments, complete the following: Select an Environment - The Site URL that displays under the eSign Administration and Settings in Nintex eSign.
  8. Click Save.

Caution: Once saved, the API user is created in Nintex eSign and is based on the app name and the creator's Salesforce org ID. For example, the format of the API user is DocGen_{org ID}_{GUID added by eSign}.

Add a Nintex eSign Delivery Option

Before you add the delivery option, you'll need to have a complete template in Nintex eSign. A complete template must have webhooks, at least one signer, and a JotBlock An area in Nintex AssureSign templates or documents that indicates where data will be applied. attached to the template. To learn more about creating a complete template in Nintex eSign, see Working With Simple Setup Templates.

Note: If your Nintex eSign delivery option is disabled when you attempt to run a DocGen Package with it, your Nintex eSign license may be expired. Check the Nintex Admin tab to review your license status.

  1. Open or Create a DocGen Package.

  2. In your DocGen Package, click the Delivery tab.

  3. In the Select Delivery Method or Storage Location pane, expand Electronic Signature and click Nintex eSign.
  4. Complete the required fields for Delivery Options. See Delivery Option fields and descriptions .
  5. Under Nintex eSign as Delivery Method:
    1. Select an eSign Account from the drop-down.
    2. Select an eSign Template from the drop-down. (Note that if you alter the template in eSign, you must click Refresh Inputs so that the changes you made are reflected in the Nintex eSign delivery method. In addition, if you alter the default Signer Identifier in eSign, special characters are not supported. Use only alphanumeric characters, spaces, and underscores, but do not use consecutive spaces and underscores. For example, Signer_1 or Signer 1 are supported, but Signer-1, Signer__1, and Signer _1 are not.)
  6. Under the Signer details, complete the fields. See Nintex eSign as Delivery Method for field details.
  7. Populate the Sender Input fields if needed. The sender inputs fields are populated from the Edit Sender Input section in Nintex eSign. (Sender Inputs are additional files that are not signed. Attachments are not sender inputs.)
  8. View and copy Nintex eSign JotBlocks:
    1. In the upper-right, open the Field Tagger.
    2. Expand Recipients. Copy all the available JotBlock tags and paste the tags in your Nintex DocGen template. The JotBlock tags are grouped by their associated signer. We recommend that all JotBlock field tags associated with the selected Nintex eSign template are pasted into a template. See Add templates to a DocGen Package
  9. Save the document and upload it to your DocGen Package under Documents > Templates.
  10. Confirm the settings and click Save.
  11. Test your delivery option.