Hi Alex, 

Here are my responses to your questions:

What gets sent back to Laserfiche as a document sent out to Docusign to get signed travels through the signature path? 

• DocuSign posts XML back to Laserfiche that includes information about the signing envelope (token info like date/time modified, signer name, any custom token values, etc). It also includes a signed PDF. 

Does a document get sent back each time the document is signed? 

• You configure when the doc gets sent back to Laserfiche on the DocuSign side. For instance, you can send an update when its' delivered, voided, singed/completed, declined, and sent (to DocuSign recipients). For the signed/completed case, the document will only be sent to Laserfiche if all required recipients sign the document. See here for more information about the DocuSign Envelope events. 

Does it get sent back as a new version?

• Yes, if you initiate the signing process from Web Access (with the 'Request DocuSign Signature' feature), the PDF will be stored as the efile component of the document and a new version will be created. If the document was not previously version controlled, Version 1 will be the original document prior to signing, Version 2 will include the signed PDF. 

Does it get sent back in the original format, a PDF, or a TIFF?

• It'll always be a PDF. If the original document was not a PDF, the importer will upload the signed PDF as the new efile component. If users work with Tiff pages primarily and want to see the signature on the PDF, you'll need to regenerate pages. 

Do then the tokens get applied to each of those versions?

• Yes, every time you sign the document, the tokens that get assigned to the corresponding version will be pulled from that signing process. In other words, the field data for the latest version will correspond to the latest signing run through.