Docmosis can generate documents that can then be used as part of an electronic signing process with DocuSign, Adobe Sign, signNow and other digital eSignature platforms.
The trick is to include the "tags" required by the electronic signing platform as part of the template. After the document generation process, Docmosis leaves the signature tags untouched, ready to be used in the next step by the e-sign service.
Here are three articles explaining the format of such tags:
- Adobe Sign: https://helpx.adobe.com/sign/help/adobesign_text_tag_guide.html
- DocuSign: https://support.docusign.com/en/guides/dfs-admin-guide-automatic-anchor-text-and-tags
- signNow: https://www.signnow.com/features/add-text-tags-to-the-document
For example the different character combinations used to identify where to place the signature for "Signer 1" are:
- Adobe Sign: "{{Sig_es_:signer1:signature}}"
- DocuSign: "\s1\"
- signNow: "{{t:t;r:y;o:“signer1”;l:“FullName”;}}"
One useful trick to "hide" the tag is to formatting the text with a color that is the same as page color (usually white). It won't be visible to a person viewing the document, but can still be read by the signing platform.
Docmosis ignores these special eSignature tags and treat them like ordinary text. They will survive the document generation process and be present in the generated document.
Docmosis does not currently send the documents to the eSignature platforms. Docmosis returns the document to your application and initiating the signing process is then performed by your application.
