.NET SDK

Hi I have been playing with embedded signing URL generations lately and originally learned from this blog post that " Once you’ve gotten an authentication token, the next step is to build the following URL to embed in the src of your iframe" So I did the following : SessionToken signerToken = EslClient.CreateSignerSessionToken(package.Id,signer.Id); string url =$"{eSignLiveUrl}/access?sessionToken={signerToken.Token}"; The above code will give a URL looking as below : https://sandbox.esignl

I was reading through the blog found at: https://www.esignlive.com/blog/esignlive-tls-support/, and what I would like to know does the 10.13 (.Net) SDK support TLS 1.2?

Hi All, I am getting the below error, while using the WithExtractionType method :

DocumentBuilder' does not contain a definition for 'WithExtractionType' and no extension method 'WithExtractionType' accepting a first argument of type 'DocumentBuilder' could be found (are you missing a using directive or an assembly reference?)

Can you please help me to resolve this bug ? Note : I am using esl-sdk-net-11.0 SDK librabry

Hi See Attachment Here's the DOCUMENT_SIGNED push notification, I can't associate the sessionUser to either signer in the Package object returned from the SDK. (see the screen shot below, I have the signer Ids boxed in red) Is this a known bug with the push notification? Can this be fixed? Thanks. { "@class":"com.silanis.esl.packages.event.ESLProcessEvent", "name":"DOCUMENT_SIGNED", "sessionUser":"8b2dc93e-9131-4714-b6f9-4fd59d7202dc", "packageId":"v3a06oosN2n8kA3uhWiH0WQkmqE=", "message":null, "documentId":"261323", "createdDate":"2018-03-04T17:30:22.740Z" }

Hello, We are setting a particular document in the package to use AcceptFor signatures. The document in question IS NOT the standard eSign consent form. It is another document that we simply want the signer to acknowledge. We are using this code: DocumentBuilder.WithSignature(SignatureBuilder.AcceptanceFor(signerEmailAddress) However during signing, the text on the buttons gives the generic "Accept" and "Opt Out" options. Is there some way to control the button text that appears to the signer for this document? Thanks, - Aaron

I saw an earlier post indicating that Bounce events are not accessible through the API. Can this be confirmed? If so, is there a suggested way to deal with this through code in the scenario that the listening service is offline at the time of the event? Thanks in advance. -Keith

Hi, I've come across a situation where a signers signing status for a particular document does not get updated when the document is declined. It can be reproduced as follows: 1. Create a package with 1 document and 1 signer. 2. Enter the signing ceremony and decline the document. 3. This puts the package into the DECLINED status 4. The signer that declined is still in the SIGNING_PENDING status (This is the bug) The following code displays how I'm retrieving the signing status for both the package and the individual signer for a document.

Should I be able to view current packages for all senders under the same account using the API key and .NET SDK? I have created a Sandbox account with an additional sender and can successfully create a new package in DRAFT passing only the secondary account as the sender. If i then execute eslClient.PackageService.GetPackages(DocumentPackageStatus.DRAFT, new PageRequest(0)) my resulting collection count is 0. Doesn't the API key have full access to the child senders under the account? Any assistance would be appreciated!

Is it possible to get data back from a package after it has been signed? For example if I have a text field on a template, after it has been filled out and signed, is there a way to get that data within my visual studio project?

Hi there, We are loading our documents in an iframe and are encountering errors with client browsers that have Third-Party Cookies disabled. Here is a sample of the error that is shown in the browser console:

Refused to display 'https://sandbox.e-signlive.ca/login?destination=/packages/ID-REMOVED=/sign' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

Is there anything we can do to get around this issue? This will be a big road block for us if we need to tell every user to manually update their browser settings and turn that setting off.