Docusignapi 添加CompositeTemplateId会导致错误

在以下JSON中添加一个compositeTemplateId会导致以下错误：

{
  errorCode: "ENVELOPE_IS_INCOMPLETE"
  message: "The Envelope is not Complete. A Complete Envelope Requires Documents, Recipients, Tabs, and a Subject Line."
}

删除

compositeTemplateId

可以防止出现错误，但出于其他原因，我需要复合模板id

{
    "emailSubject": "Please Print, Complete and Sign Document",
    "emailBlurb": "Please print and complete documents and sign on paper. ",
    "status": "sent",
    "compositeTemplates": [{
        "compositeTemplateId": "1",
        "inlineTemplates": [{
            "sequence": "1",        
            "customFields": {
                "textCustomFields": [{
                    "name": "MyOwnField",
                    "required": "true",
                    "show": "true",
                    "value": "MyValue"
                }]
            },
            "recipients": {
                "signers": [{
                    "requireSignOnPaper": "true",
                    "name": "Millard Fillmore",
                    "email": "dgilbert@firstallied.com",
                    "recipientId": "1",
                    "routingOrder": "1"
                }]
            }
        }],
        "document": {
            "documentId": "1",
            "name": "Corestone Account Application.pdf",
            "transformPdfFields": false
        }
    }]
}

如上所述，如果您在API请求的JSON部分中指定了一个compositeTemplateId值，那么请求中相应文档部分的“内容处置”值也必须为compositeTemplateId指定相同的值

如果在请求的JSON部分中指定compositeTemplateId，但在请求中相应文档部分的内容配置中指定compositeTemplateId，您将收到一条错误消息，指出信封不完整——因为DocuSign无法使用JSON中指定的compositeTemplateId值定位文档部分。因此，我怀疑您的问题是由于您当前没有在请求中文档部分的内容处置中指定compositeTemplateId值

以下请求显示了一个多部分“创建信封”API请求的示例，该请求在这两个部分中指定了相同的compositeTemplateId值：

• inlineTemplate对象（在消息的JSON部分内）

及

• 内容处置值（在消息的文档部分内）

请求示例

POST https://demo.docusign.net/restapi/v2/accounts/201105/envelopes HTTP/1.1

X-DocuSign-Authentication: {"Username":"johnDoe@gmail.com","Password":"johnsPassword!","IntegratorKey":"ABCD-eae5f282-j4k3-47c3-b293-1c4cf55b-93gh"}
Content-Type: multipart/form-data; boundary=MY_BOUNDARY
Accept: application/json

--MY_BOUNDARY
Content-Type: application/json
Content-Disposition: form-data

{
    "emailBlurb":"Test Email Body",
    "emailSubject": "Test Email Subject",
    "status" : "sent",
    "compositeTemplates": [
    {
        "compositeTemplateId": 1,
        "inlineTemplates": [
        {
            "sequence" : 1,
            "customFields": {
                "textCustomFields": [
                    {
                        "value": "1234567",
                        "required": "false",
                        "show": "true",
                        "name": "ProductId"
                    }
                ]
            },
            "recipients": {
                "signers" : [{
                    "email": "sallysEmail@outlook.com",
                    "name": "Sally Adamson",
                    "recipientId": "1",
                    "defaultRecipient": "true",
                    "emailNotification": {
                                "emailSubject": "Recipient specific subject",
                                "emailBody": "Recipient specific body"
                    }
                }]
            }
        }],
        "document": {
            "documentId": 1,
            "name": "NDA",
            "transformPdfFields": "true"
        }
    }]
}
--MY_BOUNDARY
Content-Type: application/pdf
Content-Disposition: file; filename="SampleForm.pdf"; compositeTemplateId="1"; documentid="1"

...pdf_byte_stream_here...

--MY_BOUNDARY--