OneSpan Sign Developer Community: Week in Review (August 14, 2017)
Let's take a quick look at what happened for the week of August 14th in the OneSpan Sign Developer Community.
Async Document Upload
As best practices in OneSpan Sign, it is not recommended to upload documents asynchronously (e.g. create an instance of the uploadDocument() call in multiple threads). This is mainly due to too many upload document calls being made in a short period of time for the same package. When this happens, multiple requests are trying to update a row in the database and a race condition occurs due to the number of calls being sent. What I suggest instead is to add all your documents in your document package object and use the
eslClient.createPackageOneStep() call. This will create a multipart/form-data request and upload all your documents in one request, avoiding the race condition. Link to Post
Assigning Fields using Text Tags
When adding any field to a document using the Text Tag Extraction feature, the fields become associated with the first signature on the document. This is as designed. It is mainly due to the fact that, in the future, fields will no longer be associated with signatures. Link to Post
Download Partially Signed Documents
In OneSpan Sign, you can download the documents anytime through the API and signatures will appear on the documents. However, if you’re planning to do some further processing, I would suggest downloading the flattened version, which you can only get through the REST API:
This way, your signatures will not be lost if you edit the partially signed documents. Though, you will lose the audit trail embedded in the pdf. Link to Post If you have questions regarding this blog or anything else concerning integrating OneSpan Sign 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.