9,284
edits
DocuSign integration: Difference between revisions
Jump to navigation
Jump to search
→Envelope ID
No edit summary |
|||
| Line 49: | Line 49: | ||
== Envelope ID == | == Envelope ID == | ||
In DocuSign, an envelope is a container for documents that | In DocuSign, an envelope is a container for documents that must be signed.<sup>[https://support.docusign.com/en/articles/000045001 1]</sup> We can store the envelope ID with the target entity record. If the target entity (for example, work order, appointment, or questionnaire) contains a field containing the text "DocuSignEnvelopeID" (case-insensitive), it is automatically filled with DocuSign envelope server ID. | ||
The ID can serve as a direct link between the CRM document and DocuSign Inbox. It can be used as an indicator that a document was signed. It allows further workflows like forcing documents to be signed before the entity is saved. | The ID can serve as a direct link between the CRM document and DocuSign Inbox. It can be used as an indicator that a document was signed. It allows further workflows like forcing documents to be signed before the entity is saved. | ||
Storing DocuSign envelope ID plays an important role in email-driven signing workflows. The DocuSign signing ceremony has the option '''Finish Later''' which postpones in-person signing and sends an email to the signer for later processing. In this case, it's essential to store the envelope ID to allow storing the signed document in the right place after the signer completes the signing ceremony. However, this part is the responsibility of the server-side or manual process, which must be triggered after the envelope completion is confirmed by DocuSign. | |||
== Configuring report templates == | == Configuring report templates == | ||