Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Replies
Topics Started
Preferences
Topic Started
Topics |
---|
I have setup a sandbox environment for v11 and tried out the SignDocuments() for a signer.
|
This code seem to allow dynamic creation of a group with a custom Id. However, after the group's created, it seem to reflect a different group Id.
|
Trying out the SignDocuments(packageId, signerId) call in the example throws EslServerException.
Additional information below: Could not create a signer authentication token.
|
We have different types of agreement documents and each type would require a certain content for the Electronic Disclosure Consent page.
|
Having this url allows us to embed the signing session within our website via an embedded iframe -> https://sandbox.e-signlive.com/access?sessionToken={signerAuthenticationToken}
However,
|
Replies Created
Reply to: How to use custom Electronic Disclosure/Consent content within a package
Tuesday, December 20, 2016 at 07:08amThanks - 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
Tuesday, December 20, 2016 at 01:35pmHi 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
Reply to: SignDocuments() returning "error.routeNotFound"
Thursday, January 12, 2017 at 07:02amWe're using sandbox.e-signlive.com / apps.e-signlive.com, the "e-" (e dash). Seems different from the URL you mentioned. Also has this version in the webpage;s footer - v10.13.12.
How do we move to v11? Is there a list of breaking changes with the SDK if any?
As for the ESL SDK we're using v11.0.1.0.
Reply to: SignDocuments(pkgId, signerId) throws "Could not authenticate using signer..."
Tuesday, January 24, 2017 at 04:34amHi Haris,
Here's the packageId:
2mmtw1q0u0qhz1cfV_FFgrmscNE=Thanks
Reply to: SignDocuments(pkgId, signerId) throws "Could not authenticate using signer..."
Tuesday, January 24, 2017 at 08:04amThanks Haris. Got it to work now. Was previously testing it out on top of the ESL SDK examples project (https://github.com/eSignLive/esl.sdk.net), and that's still throwing error. But then it works when i'm using a separate project directly referencing latest SDK.
Thanks again
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
I have setup a sandbox environment for v11 and tried out the SignDocuments() for a signer.
|
4 | 7 years 2 months ago | 23 | |
This code seem to allow dynamic creation of a group with a custom Id. However, after the group's created, it seem to reflect a different group Id.
|
1 | 7 years 2 months ago | 13 | |
Trying out the SignDocuments(packageId, signerId) call in the example throws EslServerException.
Additional information below: Could not create a signer authentication token.
|
3 | 7 years 2 months ago | 40 | |
We have different types of agreement documents and each type would require a certain content for the Electronic Disclosure Consent page.
|
5 | 7 years 3 months ago | 22 | |
Having this url allows us to embed the signing session within our website via an embedded iframe -> https://sandbox.e-signlive.com/access?sessionToken={signerAuthenticationToken}
However,
|
2 | 7 years 4 months ago | 45 |
Subscriptions Release Notes
This user is not subscribed to any release notes.