我在尝试从一组服务器模板(与 DS 一起存储的模板)创建信封时遇到了 DocuSign REST api (v2) 问题。我与 DS 连接,他们接受我的 JSON,但是,我收到一条错误消息:
ONESIGNALLSIGN_NOT_SATISFIED =>您的帐户不允许自由签名,因为它与其他设置冲突,请为每个签名者放置签名标签。
我也无法弄清楚消息实际上指的是什么。实际上,我没有在 JSON 请求中包含每个签名者的选项卡,只包含签名者信息和角色名称。这与我们使用 SOAP api 成功生成信封的方式非常相似(也就是说,我们不包括标签信息和每个文档的签名者信息)。
我基于我的 JSON 这个例子:
https://github.com/Ergin008/DocuSign-REST-API-Webinar-April2013/blob/master/example3.json
我对这个问题做了一些广泛的搜索和阅读,并尝试了许多不同的方法来构建每个我发现的示例的请求 JSON,但似乎这个错误阻止了任何前进的进展。我可以找到另一个与此错误斗争的人的参考的唯一其他地方是在这里:
我试图使用其中的一些信息来解决这个问题,但无济于事。我不完全确定他们用“文档可见性”等引用了什么......这可能是我的问题......
非常感谢可以提供的任何帮助!谢谢!
JSON:
{
"status": "sent",
"emailSubject": "Testing DocuSign REST",
"emailBlurb": "",
"compositeTemplates": [
{
"serverTemplates": [
{
"sequence": 1,
"templateId": "9F712D11-2524-433F-98F0-D3ADCC041B42"
}
],
"inlineTemplates": [
{
"sequence": 1,
"recipients": {
"signers": [
{
"recipientId": "28214",
"clientUserId": "28214",
"email": “test1@yahoo.com",
"name": "COLBY",
"roleName": "BORROWER1",
"requireIDLookup": false
},
{
"recipientId": "13020",
"clientUserId": "13020",
"email": “test2@YAHOO.COM",
"name": “CHEESE”,
"roleName": "BORROWER3",
"requireIDLookup": false
}
]
},
"customFields": {
"textCustomFields": [
{
"name": "PDF_CLIENT",
"value": "108"
}
]
}
}
]
},
{
"serverTemplates": [
{
"sequence": 2,
"templateId": "06E28E05-FF6F-4CD0-962A-7EBF3EE78BC5"
}
],
"inlineTemplates": [
{
"sequence": 2,
"recipients": {
"signers": [
{
"recipientId": "28214",
"clientUserId": "28214",
"email": “test1@yahoo.com",
"name": "COLBY",
"roleName": "BORROWER1",
"requireIDLookup": false
},
{
"recipientId": "13020",
"clientUserId": "13020",
"email": “test2@YAHOO.COM",
"name": “CHEESE”,
"roleName": "BORROWER3",
"requireIDLookup": false
}
]
},
"customFields": {
"textCustomFields": [
{
"name": "PDF_CLIENT",
"value": "108"
}
]
}
}
]
},
{
"serverTemplates": [
{
"sequence": 3,
"templateId": "B702BFAD-DE2C-411E-A7EF-EA1E12805341"
}
],
"inlineTemplates": [
{
"sequence": 3,
"recipients": {
"signers": [
{
"recipientId": "28214",
"clientUserId": "28214",
"email": “test1@yahoo.com",
"name": "COLBY",
"roleName": "BORROWER1",
"requireIDLookup": false
},
{
"recipientId": "13020",
"clientUserId": "13020",
"email": “test2@YAHOO.COM",
"name": “CHEESE”,
"roleName": "BORROWER3",
"requireIDLookup": false
}
]
},
"customFields": {
"textCustomFields": [
{
"name": "PDF_CLIENT",
"value": "108"
}
]
}
}
]
}
],
"eventNotification": {
"url": “oureventhandlingprogramurl”,
"loggingEnabled": true,
"envelopeEvents": [
{
"envelopeEventStatusCode": "Sent",
"includeDocuments": false
},
{
"envelopeEventStatusCode": "Delivered",
"includeDocuments": false
},
{
"envelopeEventStatusCode": "Completed",
"includeDocuments": false
},
{
"envelopeEventStatusCode": "Declined",
"includeDocuments": false
},
{
"envelopeEventStatusCode": "Voided",
"includeDocuments": false
}
]
}
}
Run Code Online (Sandbox Code Playgroud)
和回应
{
"errorCode": "ONESIGNALLSIGN_NOT_SATISFIED",
"message": "Freeform signing is not allowed for your account because it conflicts with other settings, please place signing tabs for each signer."
}
Run Code Online (Sandbox Code Playgroud)
经过一番研究,我们在 DocuSign 管理面板设置中发现了这个问题。
“文档可见性”是其中一项设置(它是一个下拉列表),将其设置为“关闭”让我们解决了这个问题。
希望这对未来的人有所帮助!
| 归档时间: |
|
| 查看次数: |
1244 次 |
| 最近记录: |