We've been using the sandbox for testing. We use the sandbox from our development machines and a server. Everything was fine until a few weeks ago. We cannot get documents signed using the test server. I know we were able to get documents signed using the test server last December. In the meantime, everything works fine from my development machine. The code for signing has not changed since last July.
I use following method to update senders info: eslClient.AccountService.UpdateSender(info, senderid); The problem is that once this is done sender is inactive and invitation needs to be sent to a sender. Is there a way to activate sender immediately after update? I think there is another option. Delete sender and then invite user: EslClient.AccountService.InviteUser(member) where member.Status = active. Please let me know if i can use first option without sending invitation or i need to use second option.
I am evaluating the use of your product and am wondering if it will accomplish the following task. I will create a sales template that is a sample invoice. Attached is the form i'm looking at. What i want to do is for each section, say Licencing fee, Support Fees and Setup and Training fees, i will have radio buttons and my sales rep will select the options for each. What i would like is to then have the form automatically populate the summary of charges section.
Hi, We've a scenario wherein we have 3 signers for a given document and all of them sign sequentially. Singer1 signs then signer2 and then signer3. The issue though is that signer2 is identified at runtime and known to signer1. i.e. when the package reaches signer1, there is a offline process that lets signer1 know who singer2 is . please provide any suggestion on how to implement this scenario... thanks Neel
Hi , I am able to connect to Sandbox from my personal laptop, while connecting from my office getting connection refused, do we need to enable open any specific port or modify any firewall settings? Could you please suggest? Error log: Caused by: org.apache.http.conn.HttpHostConnectException: Connect to sandbox.esignlive.com:443 [sandbox.esignlive.com/54.85.59.26] failed: Connection timed out: connect at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:142) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(Pooli
Could please anyone help with Opening the document to be signed in a device (like IPad or tablet ) without having the User to click on email link. Use case : Customer in Branch for account opening or any subscribing to a new product(Credit Card , Derivatives , Mortgage loan), one the all the details are entered by the branch RM , the document which require Signature should be redirected to device or e-Signlive Cloud application in the branch. In this the notification of the Signing the document shouldn't go to the Customers Mobile device but to a device in the branch.
With this https://www.esignlive.com/blog/e-signlive-how-to-setting-up-callbacks/ , it looks like callbacks can be setup via code rather than through the eSign Admin UI. Do you setup this callback each time a package for is created? Is this callback event notification short lived to the package or long lived? I was under the impression, callback setup was an account wide setup in that all calls to eSign follow a single callback url. Thanks, David