简体   繁体   English

Docusign事件通知

[英]Docusign event notifications

I am implementing a listener for Docusign event notifications. 我正在为Docusign事件通知实现一个监听器。 For each new event Docusign sends a new xml serialized DosuSignEnvelopeInformation object. 对于每个新事件,Docusign都会发送一个新的xml序列化DosuSignEnvelopeInformation对象。 My question is, does that object include only new changed statuses or if for example one of the recipients status has not changed it will still be included. 我的问题是,该对象是否仅包含新的更改状态,或者如果其中一个收件人状态未更改,则仍将包含该状态。 Also, since a change to one of the recipients status does not necessarily change the envelope status, will the notification always include the envelope status ? 此外,由于更改其中一个收件人状态不一定会更改信封状态,通知是否始终包含信封状态?

I'd recommend taking a look at the XSD: https://www.docusign.net/api/3.0/schema/dsx.xsd 我建议看看XSD: https//www.docusign.net/api/3.0/schema/dsx.xsd

The type sent by connect is DocuSignEnvelopeInformation, which consists of EnvelopeStatus and DocumentPDF objects, both of which have their schema defined in this XSD. connect发送的类型是DocuSignEnvelopeInformation,它由EnvelopeStatus和DocumentPDF对象组成,两者都在此XSD中定义了它们的模式。 In short the connect XML is a snapshot of the envelope at the time the notification is sent to you - the snapshot will include all recipient information. 简而言之,连接XML是发送通知时信封的快照 - 快照将包含所有收件人信息。

In the sandbox environment you can enable a test DS Connect configuration with logging enabled to see what types of messages you will be receiving. 在沙盒环境中,您可以启用测试DS Connect配置并启用日志记录,以查看您将接收的消息类型。

Absolutely correct and keep in mind that to save space in the demo environment we don't include the PDF byte stream in the log as it has no logic, meaning it's just a bunch of bytes. 绝对正确并记住,为了节省演示环境中的空间,我们不在日志中包含PDF字节流,因为它没有逻辑,这意味着它只是一堆字节。 If you want to see it you can use webhook.com (free) or some other tool like that. 如果你想看到它,你可以使用webhook.com(免费)或其他类似的工具。

The Connect Service and the related "eventNotification" node in the API are event-driven. API中的Connect Service和相关的“eventNotification”节点是事件驱动的。 They don't publish events, but rather, the complete current status of the envelope, which includes envelope status, recipient status for all recipients, and more. 它们不发布事件,而是发布信封的完整当前状态,其中包括信封状态,所有收件人的收件人状态等。 The service always publishes the current status , so two "near" events might trigger one coalesced status publication, or two close publications. 该服务始终发布当前状态 ,因此两个“近”事件可能会触发一个合并状态发布或两个紧密发布。 However, the last publication will include the latest changes. 但是,最后一个出版物将包括最新的变化。 If you get a "republished" status (such as due to failed acknowledgement or directly triggered), it again is the current status, not the "old" status at the time of the original publication. 如果您获得“重新发布”状态(例如由于确认失败或直接触发),则它再次是当前状态,而不是原始发布时的“旧”状态。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM