Hello, I believe there should be a possibilty for an unknown signer to exist in a Package, here's a use case from my company: A truck driver must deliver concrete to a construction zone and the person who receives the concrete must sign as well as the driver. The driver is known beforehand as he is from our company so all is fine there but the person in the construction zone is an unknown until the moment we arrive there. The current workaround is having a "ghost signer" with basically empty FirstName, LastName, and Email.
We have scenarios where we need to support/guide the user as they work through a signing ceremony. Example: Employee opens a window and starts a signing ceremony and then moves the window over to a touch screen for the customer to use. The touch screen is facing the customer and the employee is no longer aware of what is happening in the ceremony. We would like to be able to know what document the customer is on or navigating to.
We have embedded the designerView in our portal, but currently we have no way to return the customer back to the initiating screen, leading to a poor customer experience. It would be great to be able to setup a handoverURL when generating the DesignerView In alternative, implement also in the designerView the ability to generate events that we can capture from the parent page https://www.esignlive.com/blog/esignlive-event-notifier/?_ga=2.250516741.209013835.1512625729-1322670802.1512625729
For the Signing Ceremony we currently can set the HandoverUrl only when the Package is created. It would make more sense and allow more flexibility to be able to set/override the HandoverUrl when the Signing Ceremony link is generated (e.g. BuildRedirectToSigningForSigner). This would allow for example: - different redirects for the Package creator and the other signers. - different redirects in different contexts (e.g. Mobile VS Web)
Hello, Due to the security requirements of my company, we are required to use two-way SSL to communicate with eSignLive via API. Using the open Java SDK code posted in Github, it was easy to enhance com.silanis.esl.sdk.EslClient within my company to accomplish this. I enhanced the EslClient to take in an optional parameter which has configuration information needed for two way SSL.
Currently when using a text anchor to place a field or signature block, we can specify the occurrence index (i.e. 0 = use the first occurrence of the specified text. 1 = use the second occurrence of the specified text.. etc.). A great new feature would be to allow us to specify the occurrence index in reverse order (i.e. 0 = use the last occurrence of the specified text, 1 = use the second last occurrence of the specified text...
Hello, We are running into performance issues related to the considerable size of the initial load of ESignlive on devices with a weak cellular signal. I did some investigating and found that the typical first load (before cache) is about 4.1MB. I tested this against both apps.esignlive.com and sandbox.esignlive.com. In cases where we have no cache and a weak cell signal this results in load times approaching a minute or more! But I think there are some simple things that could be done to help with this and I wanted to make this post to see what you think.
Hello, During our testing of the new Version 11 enviornment we’ve Identified some enhancement requests that we would like to put out on the table. I’ve listed them in the priority of nice to have first. STATUS VIEW OF TRANSACTION – This specifically deals with the ability to view the status of where the signers are at in the transaction. In version 10 this existed and you were able to tell exactly where the signer was at in the signing process, if they had one or two more signers left ect.