TL:DR; The API works as expected with this aforementioned exception. {
I've successfully integrated the DocuSign API into our Laserfiche System. We can send documents either from docusign.com, or via the Repository API. I've also configured the Web Import Service config file to capture certain variables that are retained. This helps us identify externally initiated envelopes that may already have an existing folder structure inside the Repository. The piece I can't seem to figure out though is in regard to sending multiple documents out for signature. When they are returned, they are returned as individual files. Our needs for Docusign include appending multiple files together to generate a single result once returned having all the signatures being collected. Documents originating from the Repository, are updated in their existing location, where a wait condition on a separate workflow awaits it's field update for Signature Date.
}
There doesn't seem to be an easy way to change the returned document to the combined iteration of the contract. Though, if the document is viewed via Docusign.com they provide the option of downloading the combined version we desire.
I've done some additional research, and this appears to be possible for the API to accept calls for SOAP Method that would request the combined pdf, and this is an example I've pulled from their Reference Guide (https://www.docusign.com/sites/default/files/soap-api-guide.pdf ).
SOAPAction: "http://www.docusign.net/API/3.0/RequestPDFWithOptions"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<RequestPDFWithOptions xmlns="http://www.docusign.net/API/3.0">
<EnvelopeID>string</EnvelopeID>
<PDFOptions>
<ShowChanges>boolean</ShowChanges>
<AddWaterMark>boolean</AddWaterMark>
<IncludeCert>boolean</IncludeCert>
<CertificateLanguage>string</CertificateLanguage>
</PDFOptions>
</RequestPDFWithOptions>
</soap:Body>
</soap:Envelope>
This however does appear to be an outdated version of the API. Though I am likely to assume that since this option is available via DocuSign, and I capable of doing so with Laserfiche's API Integration? I've also seen on a previous Laserfiche Answers post that Laserfiche was not capable of generating Pages for documents received via the API. Though, the post was back in 2016, and there have been significant updates on both sides since then.
My hope is that someone whom is familiar with the Laserfiche DocuSign API may have faced and resolved this issue. I've been working on trying to resolve this for sometime. Any advice is greatly appreciated!