在信封到信封的基础上重新定义模板上的收件人角色? [英] Redefining recipient role on template on an envelope to envelope basis?

查看:68
本文介绍了在信封到信封的基础上重新定义模板上的收件人角色?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想将DocuSign模板重用于同一信封中的多个收件人.模板非常简单.它有几个签名和日期签名的块.

I want to reuse a DocuSign template for multiple recipients in the same envelope. The template is rather simple; it has a few signing and date signed blocks.

收件人将具有不同的路由顺序.据我所知,我的API请求需要使路由顺序角色名称与DocuSign模板匹配.如果角色名称和路由顺序不匹配,我将在信封上得到一个空角色(具有所有签名块).我也尝试过在草稿中合并角色".空角色将被合并到第二个收件人中,但是我丢失了该收件人的所有模板签名块.

The recipients will have different routing orders. From what I've seen, my API request needs to have the Routing Order and Role Name match the DocuSign template. If the role name and routing order don't match, I end up with an empty role (which has all of the signing blocks) on the envelope. I've also tried "merge roles on draft." The empty role will be merged into the second recipient, but I lose all of the template's signing blocks for that recipient.

是否可以使用模板来修改模板接收者角色的定义?理想情况下,我想使用完全相同的模板,但要为该模板更改该角色的路由顺序第二个收件人.我想避免在DocuSign中创建新模板,因为最终可能会出现许多组合.

Is there a way to use a template but modify the definition of the template recipient role? Ideally, I'd like to use the exact same template but change the routing order of that role for the second recipient. I'd like to avoid creating new templates in DocuSign since I could end up with many combinations.

我想完成(更新):

我想在一个信封中两次使用相同的模板.每个收件人将被分配到模板的单个副本.最后的信封应该有两个收件人,两个文档,每个收件人只能访问和查看其文档.

I want to use the same template two times in a single envelope. Each recipient will be assigned to an individual copy of the template. The final envelope should have two recipients, two documents, and each recipient will only have access and visibility to their document.

问题在于模板的角色定义了路由顺序.路由顺序"1"适用于使用模板的第一个接收者,但是第二个接收者需要路由顺序"2".(模板的角色在所有情况下都希望路由顺序为"1",但对于第二个收件人,我希望该值为"2".)

The issue is that the template's role defines the routing order. The routing order of "1" is applicable for the first recipient using the template, but the second recipient needs a routing order of "2." (The template's role expects a routing order of "1" in all cases, but I want that value to be a "2" for the second recipient.)

模板信息示例:

  • 模板名称(例如):测试模板#1
  • 角色名称:申请人1
  • 路由顺序:1(如果我未定义路由顺序,DocuSign仍将其视为"1")

示例请求:

EnvelopeDefinition envDef = new EnvelopeDefinition();

var signer1 = new Signer()
{
    RecipientId = "1",
    Name = "First User 1",
    RoleName = "Applicant 1",
    Email = "fakeemail1@email.com",
    RoutingOrder = "1"
};

var signer2 = new Signer()
{
    RecipientId = "2",
    Name = "First User 2",
    RoleName = "Applicant 1",
    Email = "fakeemail2@email.com",
    RoutingOrder = "2"
};

envDef.CompositeTemplates = new List<CompositeTemplate>();

var composite1 = new CompositeTemplate()
{
    ServerTemplates = new List<ServerTemplate>()
    {
        new ServerTemplate("1", "Test Template #1 TEMPLATE_ID_GUID_HERE")
    },
    InlineTemplates = new List<InlineTemplate>()
    {
        new InlineTemplate()
        {
            Sequence = "1",
            Recipients = new Recipients()
            {
                Signers = new List<Signer>()
                {
                    signer1
                }
            }
        }
    }

};

var composite2 = new CompositeTemplate()
{
    ServerTemplates = new List<ServerTemplate>()
    {
        new ServerTemplate("2", "Test Template #1 TEMPLATE_ID_GUID_HERE")
    },
    InlineTemplates = new List<InlineTemplate>()
    {
        new InlineTemplate()
        {
            Sequence = "2",
            Recipients = new Recipients()
            {
                Signers = new List<Signer>()
                {
                    signer2
                }
            }
        }
    }

};

envDef.CompositeTemplates.Add(composite1);
envDef.CompositeTemplates.Add(composite2);
envDef.EnforceSignerVisibility = "true";

// Code to send envelope

注意:此外,我使用的是复合模板,因为我们的信封可能会包含模板和上传文档的各种组合.

Note: Also, I'm using composite templates since our envelopes will likely have various combinations of templates and uploaded documents.

谢谢!

推荐答案

这可以通过在创建信封时传递查询参数- change_routing_order = true 来实现.因此,用于创建信封的端点将为

This can be achieved by passing a query parameter - change_routing_order=true while creating an envelope. So endpoint for creating envelope will be

https://{{EnvironmentVal}}/restapi/v2/accounts/{{AccountIdVal}}/envelopes?change_routing_order=true

请求的正文将是

要求正文:

Req Body:

其中相同的templateId-076d9062-cfc7-408b-a47f-88c4b74af62b用于相同的RoleName,但差异路由顺序和差异签名者详细信息

where same templateId - 076d9062-cfc7-408b-a47f-88c4b74af62b is used with same RoleName but diff routing order and diff Signer details

{
   "compositeTemplates": [
      {
         "inlineTemplates": [
            {
              "recipients": {
                  "signers": [
                     {
                        "email": "email+internal@gmail.com",
                        "name": "John Doe",
                        "recipientId": "1",
                        "roleName": "Signer1",
                        "routingOrder": "1"
                     }
                  ]
               },
               "sequence": "2"
            }
         ],
         "serverTemplates": [
            {
               "sequence": "1",
               "templateId": "076d9062-cfc7-408b-a47f-88c4b74af62b"
            }
         ]
      },
      {
         "inlineTemplates": [
            {
               "recipients": {
                  "signers": [
                     {
                        "email": "email+internal2@gmail.com",
                        "name": "John Doe2",
                        "recipientId": "2",
                        "roleName": "Signer1",
                        "routingOrder": "2"
                     }
                  ]
               },
               "sequence": "2"
            }
         ],
         "serverTemplates": [
            {
               "sequence": "1",
               "templateId": "076d9062-cfc7-408b-a47f-88c4b74af62b"
            }
         ]
      }
   ],
   "status": "sent"
}

这篇关于在信封到信封的基础上重新定义模板上的收件人角色?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆