如何为没有电子邮件和姓名的收件人获取嵌入式签名URL [英] How to get embedded signing URL for a recipient who doesn't have email and name

查看：78
本文介绍了如何为没有电子邮件和姓名的收件人获取嵌入式签名URL的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我的用例是，创建一个包含代理的信封以指定以下签名者的姓名和电子邮件.

My use case is, create an envelope with an agent to specify the following signer's name and email.

我通过POST {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes 创建了信封，并带有请求正文:

I created the envelop by POST {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes, with request body:

{
  "recipients": {
    "agents": [
      {
        "clientUserId": "1",
        "email": "aaa@example.com.au",
        "name": "Agent",
        "recipientId": "1",
        "routingOrder": "1"
      }
    ],
    "signers": [
      {
        "clientUserId": "2",
        "email": "",
        "name": "",
        "recipientId": "2",
        "routingOrder": "2",
        "tabs": {
          "signHereTabs": [
            {
              "anchorIgnoreIfNotPresent": "false",
              "anchorString": "Signature_anchor_1",
              "anchorUnits": "pixels",
              "anchorYOffset": "0",
              "name": "Please sign here",
              "recipientId": "1"
            }
          ]
        }
      }
    ]
  },
  "emailSubject": "DocuSign API - Signature Request on Document Call",
  "documents": [
    {
      "documentId": "1",
      "name": "{{fileName}}",
      "documentBase64": "{{fileBase64}}"
    }
  ],
  "status": "sent"
}

代理指定签名人的姓名和电子邮件地址后，我无法通过POST {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{EnvelopeId}}/views/recipient ，并带有请求正文:

After the agent specify the name and email address of the signer, I could not obtain the signing URL by POST {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/views/recipient , with request body:

{
  "clientUserId": "2",
  "userName": "",
  "email": "",
  "recipientId": "2",
  "returnUrl": "https://www.sample.com",
  "authenticationMethod": "email"
}

响应为:

{
    "errorCode": "INVALID_REQUEST_PARAMETER",
    "message": "The request contained at least one invalid parameter. A value was not found for parameter 'userName'."
}

我尝试使用新的指定名称和电子邮件来获取它:

I tried to get it with the new specified name and email:

{
  "clientUserId": "2",
  "userName": "new",
  "email": "new@example",
  "recipientId": "2",
  "returnUrl": "https://www.sample.com",
  "authenticationMethod": "email"
}

但仍然收到错误响应:

{
    "errorCode": "UNKNOWN_ENVELOPE_RECIPIENT",
    "message": "The recipient you have identified is not a valid recipient of the specified envelope."
}

我试图通过调用get envelop API来获取 recipientId ，并使用 recipientId 来检索视图，但仍然无法正常工作.

I tried to get the recipientId by calling the get envelop API and use the recipientId to retrieve the view but still not working.

如何生成此URL?应该是什么请求主体?

How can this URL be generated? What request body should it be?

更新:在以下情况下:

  1. 信封有1个代理和1个收件人，当发件人发送信封时，发件人不知道收件人的电子邮件和姓名，只有代理知道信息(这就是为什么我将名称和电子邮件放在空白处的原因收件人).
  2. 代理商收到了请求，并输入了收件人的姓名和电子邮件地址
  3. 我们希望为收件人获得该嵌入式签名链接，但现在看来，即使调用GET GET/restapi/v2.1/accounts/{accountId}/envelopes获得的信息也无法检索到该链接./{envelopeId}/收件人

更新2:

Update 2:

建议在名称和电子邮件中放置一个占位符，并在签名者中添加clientUserId，我使用请求正文调用创建信封API:

As suggested to put a place holder for the name and email and also add the clientUserId for the signer, I call the create envelope API with request body:

{
  "recipients": {
    "agents": [
      {
        "clientUserId": "1",
        "email": "aaa@example.com.au",
        "name": "Agent",
        "recipientId": "1",
        "routingOrder": "1"
      }
    ],
    "signers": [
      {
        "clientUserId": "2",
        "email": "example@example.com",
        "name": "example",
        "recipientId": "2",
        "routingOrder": "2",
        "tabs": {
          "signHereTabs": [
            {
              "anchorIgnoreIfNotPresent": "false",
              "anchorString": "Signature_anchor_1",
              "anchorUnits": "pixels",
              "anchorYOffset": "0",
              "name": "Please sign here",
              "recipientId": "1"
            }
          ]
        }
      }
    ]
  },
  "emailSubject": "DocuSign API - Signature Request on Document Call",
  "documents": [
    {
      "documentId": "1",
      "name": "{{fileName}}",
      "documentBase64": "{{fileBase64}}"
    }
  ],
  "status": "sent"
}

对于代理，他无法更改签名者的电子邮件/名称，因为当他访问DocuSign签名链接时，DocuSign会弹出一条消息"已分配所有收件人".

For the agent, he cannot change the email/name for the signer, since when he accesses the DocuSign signing link, DocuSign pops a message "All recipients have been assigned".

所以我尝试使用 intermediaries 而不是 agents 并使用请求正文进行调用:

So I tried to use intermediaries instead of agents and call with the request body:

{
  "recipients": {
    "intermediaries": [
      {
        "clientUserId": "1",
        "email": "aaa@example.com.au",
        "name": "Intermediary",
        "recipientId": "1",
        "routingOrder": "1"
      }
    ],
    "signers": [
      {
        "clientUserId": "2",
        "email": "example@example.com",
        "name": "example",
        "recipientId": "2",
        "routingOrder": "2",
        "tabs": {
          "signHereTabs": [
            {
              "anchorIgnoreIfNotPresent": "false",
              "anchorString": "Signature_anchor_1",
              "anchorUnits": "pixels",
              "anchorYOffset": "0",
              "name": "Please sign here",
              "recipientId": "1"
            }
          ]
        }
      }
    ]
  },
  "emailSubject": "DocuSign API - Signature Request on Document Call",
  "documents": [
    {
      "documentId": "1",
      "name": "{{fileName}}",
      "documentBase64": "{{fileBase64}}"
    }
  ],
  "status": "sent"
}

中介可以更新签名者的姓名/电子邮件.但是，在中介机构更改信息之后，即使已经在该请求者的请求正文中设置了 clientUserId ，DocuSign也会向更新后的电子邮件地址发送电子邮件.

The intermediary can update the name/email for the signer. But after the intermediary change the info, DocuSign will send an email to the updated email address even the clientUserId is already set in the request body for that signer.

我想知道这是否是预期的行为

I'm wondering if this is the expected behaviour:

  1. 无论中介人何时更新签名者的姓名/电子邮件，DocuSign都会将电子邮件发送到更新的电子邮件地址，无论是否为该签名者设置了 clientUserId

这可能是另一个问题，但是DocuSign似乎为签名者处理更新电子邮件事件并以不同的方式见证.我想知道我观察到的情况是预期的情况:

This might be another question, but it seems DocuSign handles the update email event for signer and witness differently. I'm wondering scenario I observed is the expected one:

  1. 当签名者更新/添加其见证人的姓名/电子邮件时，如果为该见证人设置了 clientUserId ，DocuSign将不会将电子邮件发送到更新的电子邮件地址
  1. When a signer updates/adds the name/email for his witness, DocuSign will not send the email to the updated email address if the clientUserId is set for that witness

Update3:

Update3:

使用 intermediaries 参数进行调用后，我可以通过使用请求正文进行调用来检索签名者的签名URL:

After calling with the intermediaries param, I can retrieve the Signer's signing URL by either calling with request body:

{
  "clientUserId": "2",
  "userName": "example",
  "email": "example@example.com",
  "recipientId": "2",
  "returnUrl": "https://www.google.com",
  "authenticationMethod": "email"
}

OR 

{
  "clientUserId": "2",
  "userId": {{userId retrieved from get envelope recipients}},
  "recipientId": "2",
  "returnUrl": "https://www.google.com",
  "authenticationMethod": "email"
}

但是，在中介机构更改了收件人的电子邮件/名称之后，上述请求正文都无法检索签名URL.我尝试了原始和更新的 clientId 和(电子邮件 + 名称)组合，但仍然无法正常工作.

But after the intermediary changed the email/name of the recipient, none of the above request body could retrieve the signing URL. I tried both original and updated clientId and (email + name) combination, but still not working.

我认为这是DocuSign的设计:在中介机构更改收件人的电子邮件/名称之后，不允许检索收件人的签名URL，该签名URL只能通过DocuSign发送的电子邮件获得.如果设置了 clientUserId ，则无法关闭此电子邮件.正确吗?

I assume this is a design of DocuSign: it's not allowed to retrieve the recipient's signing URL after an intermediary changes the recipient'e email/name, this signing URL can be only obtained by that email sent by DocuSign. This email cannot be turned off event the clientUserId is set. Is it correct?

更新4:根据建议，我尝试将 workflow 选项与请求正文一起使用:

Update 4: As suggested, I tried with the workflow option with request body:

{
  "recipients": {
    "intermediaries": [
      {
        "clientUserId": "1",
        "email": "aaa@example.com.au",
        "name": "Intermediary",
        "recipientId": "1",
        "routingOrder": "1"
      }
    ],
    "signers": [
      {
        "clientUserId": "2",
        "email": "example@example.com",
        "name": "example",
        "recipientId": "2",
        "routingOrder": "2",
        "tabs": {
          "signHereTabs": [
            {
              "anchorIgnoreIfNotPresent": "false",
              "anchorString": "Signature_anchor_1",
              "anchorUnits": "pixels",
              "anchorYOffset": "0",
              "name": "Please sign here",
              "recipientId": "1"
            }
          ]
        }
      }
    ]
  },
  "workflow": {
    "workflowSteps": [
      {
        "action": "pause_before",
        "itemId": "2",
        "triggerOnItem": "routing_order"
      }
    ]
  },
  "emailSubject": "DocuSign API - Signature Request on Document Call",
  "documents": [
    {
      "documentId": "1",
      "name": "{{fileName}}",
      "documentBase64": "{{fileBase64}}"
    }
  ],
  "status": "sent"
}

我只能在路由顺序2之前暂停工作流程，因为如果我放置 workflow 参数以实现"在中间收件人之后立即插入工作流程暂停"，则会出现400错误":

I can only pause the workflow before routing order 2, since there would be a 400 error if I put the workflow param as to achieve "insert a workflow pause immediately after the intermediaterecipient":

  "workflow": {
    "workflowSteps": [
      {
        "action": "pause_after",
        "itemId": "1",
        "triggerOnItem": "routing_order"
      }
    ]
  },

中间收件人更新名称/电子邮件后，我进行了API调用，以设置签名者的 clientUserId ，它可以正常工作.但是我无法通过请求请求调用URL {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}?resend_envelope = true 来恢复工作流正文:

After the intermediate recipient updated the name/email, I did an API call to set the clientUserId for the signer and it works fine. But I was not able to resume the workflow by calling URL {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}?resend_envelope=true with request body:

{
    "workflow": {
        "workflowStatus": "in_progress"
    }
}

签名人的状态保持为创建，并且无法更新为已发送，因此无法获取签名人的签名URL.我们如何才能取消暂停工作流程?

The status of the signer stayed as created and could not be updated to sent, thus could not retrieve the signing URL for the signer. How can we unpause the workflow?

推荐答案

座席填写收件人的姓名和电子邮件后，Docusign会自动发送该收件人的电子邮件.我想知道是否可以关闭此电子邮件?

After the Agent fill in the name and email for the Recipient, Docusign automatically sent out an email for that Recipient. I'm wondering whether this email can be turned off?

更好的办法是为代理提供一个应用程序，使他们可以设置收件人的姓名/电子邮件.该应用程序还将设置client_user_id属性，以便不发送电子邮件.

Much better would be to give the agent an application that lets them set the name/email of the recipient. The application would also set the client_user_id attribute so emails are not sent.

需要姓名和电子邮件吗?是的，但是如果您不知道此人的电子邮件(并且您正在使用嵌入式签名)，那么您可以组成一封包含签名者姓名并使用 example.com 域的电子邮件，因为该域确实可以不存在.例如，如果签名者是Pat Johnson，则使用patjohnson@example.com作为电子邮件地址.

Is a name and email required? Yes, but if you don't know the person's email (and you are using embedded signing) then you can make up an email that includes the signer's name and uses the example.com domain since that domain does not exist. Eg If the signer is Pat Johnson then use patjohnson@example.com as the email address.

还请记住，如果您没有签名人的电子邮件地址，那么您(与法律顾问进行讨论)可能需要某种方式让签名人获得其签名内容的副本.通常，DocuSign通过发送到该人的电子邮件来做到这一点.但是，如果您知道该电子邮件是伪造的，则需要一个不同的计划.

Also remember that if you don't have the signer's email address, then you probably (discuss with your legal counsel) need some way for the signer to obtain a copy of what they signed. Normally DocuSign does this by sending to the person's email. But if you know that the email is fake, you'll need a different plan.

我相信，当 intermediary 收件人设置签名者的姓名/电子邮件时，签名者的属性(包括client_user_id)将被重置.因此，签名者会收到邀请电子邮件，因为他们(目前)是常规签名者.

I believe that when the intermediary recipient sets the name/email of the signer, the signer's attributes, including the client_user_id are being reset. So the signer receives the invite email since they're (at this point) a regular signer.

一种解决方法是插入工作流程暂停.然后使用该暂停将签名者更改为具有client_user_id.

One fix is to insert a workflow pause immediately after the intermediaterecipient. Then use that pause to change the signer to have a client_user_id.

这篇关于如何为没有电子邮件和姓名的收件人获取嵌入式签名URL的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！

查看全文
相关文章
其他开发最新文章
热门教程
热门工具
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆