.NET SDK

I have setup a sandbox environment for v11 and tried out the SignDocuments() for a signer. However, I’m getting this error:

An unhandled exception of type 'Silanis.ESL.SDK.EslException' occurred in Silanis.ESL.dll
Additional information: Could not authenticate using a signer authentication token. Exception: Object reference not set to an instance of an object.

For this call:

SignDocuments(PackageId packageId, string signerId) 
> AuthenticationService.GetSessionIdForSignerAuthenticationToken

Thanks

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. Is there a way to create a group with a preset Id value?

GroupBuilder.NewGroup(groupName).WithId(new GroupId(groupId))

Just for context, need this to work as we're using .EnableExtraction() convenience in auto-generating signers including that of an internal group. Would like to establish the same groupId reference in both sandbox and production environment, so we have to maintain only single copy of document template.

Trying out the SignDocuments(packageId, signerId) call in the example throws EslServerException. Additional information below: Could not create a signer authentication token. Exception: The remote server returned an error: (404) Not Found. HTTP POST on URI https://sandbox.e-signlive.com/api/authenticationTokens/signer/multiUse.

Hi, Your code samples are not showing on your getting started pages eg: Creating and Sending a Package (.NET) Can you fix? Cheers, Mark

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?

Hi, I got an email from eSignLive today saying that, effective January 9 of 2017, all transactions older than 90 days will be moved from the cloud to another database. I'm trying to figure out what this means for our company. Right now, we keep all transactions so that the user can both see and download completed transactions. Will this new update break all the transactions older than 90 days? This could cause some issues. Any further explanation will be appreciated. Thank you, Fernando

Hello, I recently updated the api version for Silanis.ESL.dll from 10.3 to 10.13, after doing so the code that I'm using to dynamically build the packages for getting signed no longer works.

Hi Team, We have tried SignatureFor method and CaptureFor method we did not find any difference in the behavior (Where CaptureFor is expected to capture the signature for that document again which is not reflected) Here is the implementation For CaptureFor and SignatureFor doc.WithSignature(SignatureBuilder.CaptureFor(email) .WithName(signature.Signer.Role.ToString()) .OnPage(signature.Page - 1) .AtPosition(signature.X * CONVERSION_FACTOR, signature.Y * CONVERSION_FACTOR) .WithSize(signature.Width * CONVERSION_

Hi! In some cases, I would like to send a document package with no signers but only reviewers. Those users will only have to "review" the document without signing it. I have tried to keep the users as "Signers" but below is the error message I am getting: "{\"messageKey\":\"error.validation.sendPackage.noApprovals\",\"message\":\"Cannot send package without approvals.\",\"code\":400,\"name\":\"Validation Error\"}" Should I ad them as placeholders instead ?

I am responding to certain inbound notification events (i.e. DOCUMENT_SIGNED and SIGNER_COMPLETE) by making outbound calls using the SDK. For instance, when I get a SIGNER_COMPLETE notification, I make a call out to eSignLive to verify the status of all signers and retrieve the signed documents. It appears that when I make the outbound call to eSignLive that the status information has not yet been updated and I get the old status. It seems like a classic race condition. If I check manually a few minutes later I get the correct status.