The topic "SignNow Workflow Sample - Multiple Signers" is not available in Version 3.5.

The topic "SignNow Workflow Sample - Multiple Signers" is not available in Version 3.6.

SignNow Workflow Sample - Multiple Signers

The following procedure details a sample workflow and forms for a sequence that contains multiple signers.

Prerequisites

  1. The SignNow properties are configured in Forms Builder. See SignNow Settings.

  2. A form sequence is created. In our example, the sequence includes the following forms:

    1. Welcome

    2. TE_Personal_Info_Multi — This is an admissions application form that collects the personal data of a student and contains four SignNow components (signature and date fields for two signers).

      The signing process for the primary signer is the same as described in SignNow Workflow Sample - Single Signer. The signing process for the primary signer is an embedded process within the form window. For the secondary signer, SignNow sends an email along with the document to be signed to the secondary signer. The signing process for primary and secondary signer takes place within the same SignNow request. SignNow returns events when each signer signs the document and when the document is complete. The workflow responds to these events.

    3. SignNowCoSigner — This form informs the student that a co-signer is needed and provides three text boxes for the co-signer's first name, last name, and email address.

    4. Default-Frame — This form contains an IFrame component.

      alert We recommend that you copy the original Default-Frame form, edit the copy, and use it in your sequences. Save a backup copy of your form.

      In your copy of the form, edit the Name property as shown below (case sensitive). Keep the URL property as {{vm.models.frameUrl}}.

      Name = signNowFrame

    5. Default-DocuSignWait — This form is provided with the Forms Builder installation. For this example, we have copied and renamed it to form to SignNowWait. It contains two HTML components.

      The first HTML component displays the following text. Edit the text in your copy of the form. 

      "Current user may close this browser tab. This page will auto submit when all the signatures are collected from DocuSign."

      The second HTML component contains JavaScript code that is not applicable to SignNow. Remove that HTML component in your SignNowWait form.

      alert The Default-DocuSignWait form will be overwritten when Forms Builder is upgraded.  Copy the original form, rename it to SignNowWait, edit the copy, and use it in your sequences. Save a backup copy of your form.

      This logic can be repeated as needed for additional signers.

To optimize the display of your e-signature forms on mobile devices, you may want to add the CSS described in this Note.

Test the Multiple Signer Feature

To test the multiple signature feature with SignNow, the test environment needs to meet specific requirements. SignNow will try to call APIs on Renderer when secondary signers complete their signing process via email. This feature is referred to as Webhook.

  • If you are testing with a SignNow account in test mode:

    • Renderer must be hosted on port 80 or 443.

    • Port 80 or 443 must be open on the firewall depending on which port Renderer is using for SignNow to communicate. You can request an exception from your IT team for port 80 or 443 for an IP address range.

  • If you are testing with a live SignNow account:

    • Renderer must be hosted on port 443 (https).

    • If hosting Renderer on port 443 is not possible, a SignNow representative for your account will have to make an exception.

To confirm that multi-signature forms are completing the workflow process, please confirm that Webhook responses are received and displayed in the log. For more information, see Webhook Responses for Multiple Signer Sequences.

Chrome Browser Settings for Multiple Signers

The multiple signer feature for SignNow requires a specific setting in Google Chrome. If you experience issues with multiple signer forms, ensure that third-party cookies are allowed.

  1. In Chrome, select Settings.

  2. Click Advanced at the bottom of the page.

  3. Expand Site Settings.

  4. Expand Cookies and site data.

  5. Disable Block third-party cookies.

    Chrome Settings

Create the Workflow

SignNow provides signers the Decline To Sign option. Closed

Decline

If the decline option is selected by the primary, secondary, or any additional signer:

  • The signer will see a popup stating "You've declined to sign <PDF name>. <SignNow account email address> has been notified of your decision. You can always sign the document later if you change your mind."

  • SignNow will not return control of the sequence to Forms Builder and the workflow will not continue. The workflow will remain as a persisted instance. You will need to terminate persisted workflows periodically using either Sequence Designer (see Delete Persisted Workflow Instances) or Workflow Composer (see Persisted Workflows).