Docusign Not Generating Multiple Embedded Recipient Views

Question

I am using the Docusign Rest API, through a gem for Rails. I have 2 recipients, and need both of them to sign the document.

It should work like this:

Generate envelope with borrower(s) info passing to the envelope.
Display embedded document for signing.
Return to custom url/action
If there is another signer, it should
- reload the iframe
- ask for second signers signature, with the same template that was just signed

Instead it breaks when I reloads the iframe for the 2nd signer. It generates the envelope, with my second signer with its unique ID, email etc. However when I then create the recipient view, it returns nil.

How do I get signer 1 to sign, then load it for the second signer right after, with all the custom fields filled both times?

def deliver(signing_borrower)

    client = DocusignRest::Client.new
    hashData = {
      status: 'sent',
      template_id: my_id
      signers: [
        {
          embedded: true,
          name: signing_borrower.name,
          email: signing_borrower_email,
          role_name: if (signing_borrower==borrower) then 'Borrower' else 'Co-borrower' end
        }
      ]
    }
    generate_liabilities
    hashData[:signers][0][:tabs] = if (signing_borrower==borrower) then custom_fields else co_borrower_custom_fields end


    #if there is a coborrower, add that data to the form as the second signer
    if co_borrower
      if signing_borrower==co_borrower then opposite_of_signing_borrower = borrower else opposite_of_signing_borrower = co_borrower end

      borrower2= {
        name: opposite_of_signing_borrower.name,
        email: signing_borrower_email(opposite_of_signing_borrower),
        role_name: if (opposite_of_signing_borrower==co_borrower) then 'Co-borrower' else 'Borrower' end
      }

      #add second borrower to hash to generate envelope with all form fields filled
      hashData[:signers] << borrower2
      hashData[:signers][1][:tabs] = {
          textTabs: text_tabs,
          checkboxTabs: checkbox_tabs
        }
    end


    response = client.create_envelope_from_template hashData
    self.envelope_id = response["envelopeId"]
    self.signing_url = DocusignRest::Client.new.get_recipient_view({
      envelope_id: self.envelope_id,
      name: signing_borrower.name,
      email: signing_borrower_email(signing_borrower),
      return_url: return_url
    })

    response
  end

The hashData

{:status=>"sent",
 :email=>
  {:subject=>"Application...",
   :body=>"please sign...."},
 :template_id=>"XXXX-XXXX-XXXX",
 :signers=>
  [{:embedded=>true,
    :name=>"DAVID L. TESTCASE",
    :email=>"email@test.com",
    :role_name=>"Borrower",
    :tabs=>
     {:textTabs=>
       [{:tablabel=>"phone",
         :name=>"phone",
         :value=>"717-717-7171"}]
     }
   },
   {:name=>"MARISOL TESTCASE",
    :email=>"email2@test.com",
    :role_name=>"Co-borrower",
    :tabs=>
      {:textTabs=>
         [{:tablabel=>"phone",
         :name=>"phone",
         :value=>"717-717-7171"}]
     }
  }]}

Kim Brandl · Accepted Answer

You can accomplish what you're trying to do by making 3 API calls:

Create Envelope request, specifying both recipients as 'embedded/captive' by setting clientUserId property for each recipient.
POST Recipient View request to get the URL to launch the first signer's signing session.
POST Recipient View request to get the URL to launch the second signer's signing session.

Here's example JSON for those three calls.

1 - Create Envelope Request

POST https://{{env}}.docusign.net/restapi/{{version}}/accounts/{{acctId}}/envelopes

{
  "emailSubject": "Please sign this",
  "emailBlurb": "Please sign...thanks!",
  "templateId": "064A7973-B7C1-41F3-A2AD-923CE8889333",
  "status": "sent",
  "templateRoles": [
   {
      "roleName": "Borrower",
      "name": "John Doe",
      "email": "johnsemail@outlook.com",
      "recipientId": "1",
      "clientUserId": "123",
      "tabs":{
            "textTabs":[
               {
                  "tabLabel":"BorrowerPhone",
                  "value":"717-717-7171"
               },
            ],
         }
    },
    {
      "roleName": "Co-borrower",
      "name": "Jane Doe",
      "email": "janesemail@outlook.com",
      "recipientId": "2",
      "clientUserId": "567",
      "tabs":{
            "textTabs":[
               {
                  "tabLabel":"Co-borrowerPhone",
                  "value":"717-717-7171"
               },
            ],
         }
    }
  ]
}

A successful response will contain the Id of the newly created Envelope.

2 - POST Recipient View (for the First Recipient)

Make this call when the first signer is ready to sign. In the request URL, {{envelopeId}} is the Envelope Id value that was returned in the response of the Create Envelope request, and information in the request body corresponds to info you submitted for the first recipient in the Create Envelope request.

POST https://{{env}}.docusign.net/restapi/{{version}}/accounts/{{acctId}}/envelopes/{{envelopeId}}/views/recipient

{
     "authenticationMethod": "Email",
     "clientUserId": "123",
     "userName": "John Doe",
     "email": "johnsemail@outlook.com",
     "returnUrl": "http://www.google.com"
}

The response will contain the URL that can be used to launch the DocuSign Envelope for the first recipient.

3 - POST Recipient View (for the Second Recipient)

Make this call when it's time for the second signer to sign. In the request URL, {{envelopeId}} is the Envelope Id value that was returned in the response of the Create Envelope request, and information in the request corresponds to info you submitted for the second recipient in the Create Envelope request.

POST https://{{env}}.docusign.net/restapi/{{version}}/accounts/{{acctId}}/envelopes/{{envelopeId}}/views/recipient

{
     "authenticationMethod": "Email",
     "clientUserId": "567",
     "userName": "Jane Doe",
     "email": "janesemail@outlook.com",
     "returnUrl": "http://www.google.com"
}

The response will contain the URL that can be used to launch the DocuSign Envelope for the second recipient.

Docusign Not Generating Multiple Embedded Recipient Views

Answers (2)

Related Questions