chris-josongmail-com

How to use custom Electronic Disclosure/Consent content within a package

0 votes
We have different types of agreement documents and each type would require a certain content for the Electronic Disclosure Consent page. We're not able to use templates since each agreement has custom data that we pre-generate in the document. Couple of questions: 1) is there a way to create templates for just the Esign Disclosure Content page? 2) Or if not, how can we programmatically specify a custom Disclosure Consent content via the SDK Would prefer to take the templated Consent approach (#1 in the above options) if that's possible, so we don't have to resubmit that static content repeatedly.

Approved Answer

Reply to: How to use custom Electronic Disclosure/Consent content within a package

0 votes
Hi Chris, I believe it might be a restriction on creating a package from a template. All the examples I found didn't include adding documents. It is possible that's how it is intended to work. Though, you could do the following as a workaround:
PackageId packageId = new PackageId("-NroK8Y5KTrrciQe4eQ4IXKV2aY="); //id of the package you created from your template

Document doc = DocumentBuilder.NewDocumentNamed("test")
                .FromFile("C:/Users/hhaidary/Desktop/PDFs/doc1.pdf")
                .Build();

 Document uploadedDoc = eslClient.UploadDocument(doc, packageId);
Haris Haidary OneSpan Technical Consultant

Reply to: How to use custom Electronic Disclosure/Consent content within a package

0 votes
Hi Chris, 1) Since you said that you will have custom data that you will pre-generate in each agreement for every transaction, then you will have to upload this document to eSignLive every time right? Templates will not be of any use to you since you will only be able to create a transaction from the static document in the template. 2) You can follow this guide on how to create a consent document: https://developer.esignlive.com/guides/feature-guides/create-consent-document/. And as an FYI, you can't have one signer accept the agreement and another signer sign it. You will get an error when trying to send the package. Hope this helps.
Haris Haidary OneSpan Technical Consultant

Reply to: How to use custom Electronic Disclosure/Consent content within a package

0 votes
Thanks - appreciate the quick response, Haris. On #1, since there will be no custom data in the consent page but just different verbiage depending on the agreement type, i thought that can reside as static templates to choose from and just upload the actual [locally generated] document agreement for each signing transaction. Thanks for referring me to the consent-related article. Will look into that.

Reply to: How to use custom Electronic Disclosure/Consent content within a package

0 votes
Ah yes, in that case it definitely one way to go. You can have multiple templates with each having a different agreement. Then, you can create a package from the template and subsequently upload documents to sign, add signers, etc.
Haris Haidary OneSpan Technical Consultant

Reply to: How to use custom Electronic Disclosure/Consent content within a package

0 votes
Hi Haris, I tried the following but can't get it to work: 1) created a couple of templates, each with just a single document marked as "for disclosure / accept only" 2) whipped-up a code to read one of these templates, created new package with one dynamically-generated document using .WithDocument(...) call, and obtained delta/resultant package using eslClient.CreatePackageFromTemplate(templateId, newPackage). However, when i go to the signing session, it only shows the disclosure page. The 2nd document i added on the fly during package creation doesn't get added. Is this a restriction imposed by the template because it's defined to only have 1 document? Should the templates be defined to have 2 document whereas the 2nd document can be overriden/replaced with local document to be uploaded for each transaction? Thanks

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off