.NET SDK

Hi! I am having trouble when placing the signature tab location. Here is my code Signature signHere = SignatureBuilder .SignatureFor(signer.Email) .OnPage(Convert.ToInt32(pageNumber) - 1) .AtPosition(45, 424) .Build(); As you can see , I specify 424 for the Y axis. However, in the attached screenshot of the signed document, you can see that the signature tab is located way below 360 !!! Is there an offset somewhere I forgot to set ?

Hi! When sending some eSignLive packages (.NET SDK), here is the error message I receive for some of the packages I send (it works for others :-S) What does it mean that my document could not be flattened ? is there a preprocessing I should be doing so that the document can be flattened ? Thanks {Silanis.ESL.SDK.EslServerException: Could not upload document to package. Exception: The remote server returned an error: (400) Bad Request. HTTP POST on URI https://sandbox.esignlive.com/api/packages/PZexo1N_8CWKktm9F0xlmeoarug=/documents.

Hello! I am attempting to customize the message that is displayed in the OnDialogComplete box that is shown to a user once they're finished signing. I see in this post: https://developer.esignlive.com/forums/topic/completed-signing-message/ support says it's possible, but gives no examples.

Hi! I am trying to create an eSignLive package using the C# SDK. Below is the error I get when "sending" my package.

Hello, I had successfully set up a callback on Package Completed in my Development environment that worked fine, now I have moved to a beta test server that is using SSL and the call back is failing? In the Sandbox I have a url https://myurl and I have a Callback Key But my last two test sent an email saying failed to Failed to communicate with the callback server. URL: https://myadbeta.trilogyir.com/ADFile/SaveSignedFile Payload: {"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_COMPLETE","sessionUser":"7c521a78-a512-4d3e-9cd6-1485d78e3f7c","packageId":"36599759

Hi, I've been trying to send multiple packages asynchonously. After some testing, I discovered that it cannot truly run in parallel because EslClient.CreatePackage(DocumentPackage) acts as a bottleneck for my application. I figured that it must use some kind of lock mechanism to allow only one call at a time. So here are my questions.

1. Why is there a lock in the CreatePackage function?
2. Is there a way to work around it using the .Net SDK?
3. If not, is there a way to do it with the REST API?

Thank you.

Hi, I've notice that I can make a document "Accept Only" in the eSignLive sandbox dashboard transaction creation page. I can simply click Accept Only and select the recipients I wish to accept the document and thats it. No need for signature, only acceptation. Thing is, I can't figure out how to do it with the .Net SDK. I've looked through the Integrator's Guide, done research in the Github repository and looked through most of the SDK. What am I missing and how can I make a document "Accept Only" programmatically with the .Net SDK. Thanks alot

I am making good progress on my project I am now at a point were I want to have my app download the document after the signing is complete. To do this I would like to set up a call back event on PACKAGE_COMPLETE My dev environment is local 127.0.0.1 with a local host name How can I test the callback from the sandbox against my local IIS This is my local host name https://myphr.ad.dev/ and I would like the call back to hit a Controller Action like this https://myphr.ad.dev/eSign/SaveSignedFile Is this possible?

We have a service setup to get the "SIGNER_COMPLETE" notification but we need to iterate through and see who has signed and who hasn't. Is there a way in the .net code to get which signers are complete or at least which documents they have signed in the package?

If I assign a reminder schedule to a package with multiple signers will all the reminder schedules be applied to all the signers in order? Case:

   reminderScheduleToCreate = ReminderScheduleBuilder.ForPackageWithId(packageId)
      .WithDaysUntilFirstReminder(2)
      .WithDaysBetweenReminders(1)
      .WithNumberOfRepetitions(5)
      .Build();

Singer 1 signs the document 2 days after the document is sent - 1st singer got reminder on day 2 Singer 2 receives first reminder 2 days after Signer 1 signed the document - and signs the document that day.