Week In Review: Developer Community - March 20, 2017
Let's take a quick look at what happened for the past week in the Developer Community.
Proxies and Network Security
Using proxies definitely has its advantages. For example, it improves security, especially when used in business networks. Proxies can be used to block access to malicious attacks and they can also provide encryption services so that your data is not easily sniffed by third-parties that want to get their hands on it. However, if you are to go this route, you will need to make sure with your IT department that incoming/outgoing traffic is allowed to eSignLive. For example, you may need to add authentication for your proxy. Link to Post
Troubleshooting Text Anchors
The text anchor extraction feature allows you to position a field or signature based on the text in the uploaded document. Taking advantage of this feature can potentially save you a lot time in development if, for example, you compare it with positioning of signatures/fields using x-y coordinates. Though, a mistake can easily be made as the exact string will be searched in your document. In other words, say you want to position a signature on your document next the text "Please Sign Here" and in your payload you define "please sign here", then an error will be thrown. The exact string present in your document needs to be defined in your payload/code. Link to Post
DELETE Request Response
Deleting a package in eSignLive is a straightforward process. If you are using one of our SDKs, it's a one liner:
eslClient.getPackageService().deletePackage(packageId); //Java eslClient.PackageService.DeletePackage(packageId); //.NET
Or if you going through the REST API route, you will need to making the following call:
DELETE /api/packages/{packageId} HTTP/1.1
Host: sandbox.esignlive.com
Authorization: Basic api_key
Accept: application/json
Content-Type: application/json
In both cases, you will get a 200 OK response with an empty body. Note that deleting a package will permanently remove it from our databases and you will not be able to retrieve it at a later point. Link to Post
PDF Reader or PDF Viewer?
Lately, one of the most common issues reported by signers is the one where they cannot view the signatures in the signed documents. When downloading signed documents, you will need to use a PDF reader (preferably Adobe Reader) as it offers all the features necessary to read PDF documents and view the signatures. In addition, an extensive audit trail is embedded inside the document, for which can only be viewed in a PDF reader. When using an PDF viewer (e.g. Mac Preview), you may not experience consistent behavior.
If you have questions regarding this blog or anything else concerning integrating eSignLive into your application, visit the Developer Community Forums: developer.esignlive.com. That's it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn.
Haris Haidary Junior Technical Evangelist LinkedIn | Twitter
