- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我想知道在使用面对面签名时是否可以禁用向主持人发送电子邮件通知。 (向您发送了一份文件以主持面对面的签名 session 。)
复制:
1 - 信封是使用包含 3 个收件人的 API 创建的:一个现场专属签名者和两个远程签名者。
2 - 主持人收到电子邮件通知。
In-Person Sign Email Notification
JSON:
`{
"status":"sent",
"emailSubject":"Contract",
"compositeTemplates":[
{
"serverTemplates":[
{
"sequence":"1",
"templateId":"<templateId>"
}
],
"inlineTemplates":[
{
"sequence":"1",
"recipients":{
"inPersonSigners":[
{
"hostEmail":"johndoe@email.com",
"hostName":"John Doe",
"signerName":"Ringo Starr",
"signerEmail":"ringostarr@email.com",
"roleName":"Signer 1",
"recipientId":"1",
"clientUserId":"1000",
"routingOrder":"1",
"embeddedRecipientStartURL":"SIGN_AT_DOCUSIGN",
"recipientSignatureProviders":[
{
"signatureProviderName":"UniversalSignaturePen_OpenTrust_Hash_TSP",
"signatureProviderOptions":{
"sms":"<phoneNumber>"
}
}
]
],
"signers":[
{
"name":"John Doe",
"email":"johndoe@email.com",
"emailNotification":{
"emailSubject":"Contract for live in person signature attached.",
"emailBody":"Contract for live in person signature attached.",
"supportedLanguage":"en"
},
"roleName":"Signer 2",
"routingOrder":"2",
"recipientId":"2",
"recipientSignatureProviders":[
{
"signatureProviderName":"UniversalSignaturePen_OpenTrust_Hash_TSP",
"signatureProviderOptions":{
"sms":"<phoneNumber>"
}
}
]
},
{
"name":"Paul McCartney",
"email":"paulmccartney@email.com",
"emailNotification":{
"emailSubject":"Contract for live in person signature attached.",
"emailBody":"Contract for live in person signature attached.",
"supportedLanguage":"en"
},
"roleName":"Signer 3",
"routingOrder":"2",
"recipientId":"3",
"recipientSignatureProviders":[
{
"signatureProviderName":"UniversalSignaturePen_OpenTrust_Hash_TSP",
"signatureProviderOptions":{
"sms":"<phoneNumber>"
}
}
]
}
]
},
"customFields":{
"textCustomFields":[
{
"value":"<salesforcecontractId>",
"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"
}
]
}
}`
因为我使用的 URL 可以从我的应用程序访问,所以不需要向主机发送电子邮件通知。
注意事项:
问候。
最佳答案
从 inPerson 收件人定义中删除 "embeddedRecipientStartURL":"SIGN_AT_DOCUSIGN"
。
指定 embeddedRecipientStartURL
会使收件人也收到一封正式的 DocuSign 电子邮件,邀请他们签署文档。看这个answer想要查询更多的信息。
来自官方Documentation
embeddedRecipientStartURL is a sender provided valid URL string for redirecting an embedded recipient. When using this option, the embedded recipient still receives an email from DocuSign, just as a remote recipient would, but when the document link in the email is clicked the recipient is redirected, through DocuSign, to this URL to complete their actions. When routing to the URL, it is up to the sender's system (the server responding to the URL) to then request a recipient token to launch a signing session.
关于docusignapi - 禁用个人签名者向主持人发送电子邮件通知,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/45677154/
在我的课上,我有以下声明: class OCLState { //Irrelevant stuff involving OpenCL contexts and command queues a
我是一名优秀的程序员,十分优秀!