Docusign API生成的信封未遵循路由顺序 [英] Docusign API generated envelope is not following routing order

问题描述

我使用复合模板生成混合仪式信封：

I generate a mixed ceremony envelope using a composite template:

{
"status": "sent",
"emailBlurb": "testing creation from template",
"emailSubject": "Please sign this template",
"compositeTemplates": [{
        "serverTemplates": [{
                "sequence": "1",
                "templateId": "3f35423e-884a-4bf2-a9b5-19eaac4a5b8f"
            }
        ],
        "inlineTemplates": [{
                "sequence": "1",
                "recipients": {
                    "inPersonSigners": [{
                            "name": "LLLLL",
                            "email": "[e-mail]",
                            "hostemail": "[e-mail]",
                            "hostname": "LLLLLL",
                            "roleName": "Signer 1",
                            "recipientId": "1",
                            "clientUserId": "1000",
                            "signerName": "John Signer",
                            "signerEmail": "[e-mail]",
                            "requireIdLookUp": "true",
                            "idCheckConfigurationName": "SMS Auth $",
                            "smsAuthentication": {
                                "senderProvidedNumbers": ["[phone]"]
                            }
                        }
                    ],
                    "signers": [{
                            "name": "VVVVVVV",
                            "email": "[e-mail]",
                            "roleName": "Signer 2",
                            "clientUserId": "2000",
                            "routingOrder": "2",
                            "recipientId": "2"
                        }, {
                            "name": "ZZZZZ",
                            "email": "[e-mail]",
                            "roleName": "Signer 3",
                            "clientUserId": "3000",
                            "routingOrder": "3",
                            "recipientId": "3"
                        }
                    ]
                },
                "customFields": {
                    "textCustomFields": [{
                            "value": "8009E0000006Qu5QAJ",
                            "required": "false",
                            "show": "false",
                            "name": "##SFContract"
                        }
                    ]
                },
            }
        ]
    }
],
"eventNotification": {
    "RecipientEvents": [{
            "recipientEventStatusCode": "Completed"
        }, {
            "recipientEventStatusCode": "sent"
        }, {
            "recipientEventStatusCode": "delivered"
        }, {
            "recipientEventStatusCode": "declined"
        }
    ],
    "EnvelopeEvents": [{
            "envelopeEventStatusCode": "Delivered"
        }, {
            "envelopeEventStatusCode": "completed"
        }, {
            "envelopeEventStatusCode": "sent"
        }, {
            "envelopeEventStatusCode": "Declined"
        }
    ]
}
}

模板的第一个签名者为In Person Signer（路由顺序1），第二个签名者为两个电子邮件签名者（路由顺序2）

The template has an In Person Signer as the first signer (routing order 1) and two e-mail signers as second signers (routing order 2)

如果我从模板本身或从Salesforce开始此过程，当亲自签署仪式完成时，它将发送电子邮件以供其他两个签署者完成，但是如果从此获取签署网址，则不会发生这种情况。信封。如果我在Docusign中检查文档状态，则它正在等待第二个和第三个签名。

If I start this process from the template itself or from salesforce, when the in person signing ceremony is finished, it sends the e-mails for the other two signers to complete, but this doesn't happen if the signing url is taken from this envelope. If I check the document status in Docusign, it's waiting for the second and third signatures.

我需要具有SMS Auth（因此需要组合模板和API生成）和一个

I need to have SMS Auth (thus the composite template and API generation) and an in person signer with two e-mail signers.

我是否在信封生成中缺少某些东西才能继续进行操作？

Am I missing something in my envelope generation for the process to continue?

谢谢！

推荐答案

要发送电子邮件，请删除 clientUserId 来自签名者的参数。此参数表示签名者是嵌入式签名者。

For emails to be sent remove the clientUserId parameter from the Signers. This parameter indicates the signer is an embedded signer.

这篇关于Docusign API生成的信封未遵循路由顺序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！