OneSpan Sign Developer Community: Package Attributes and Watermarks
In this blog, I will walk you through what you might have missed in the OneSpan Sign Developer Community during the week of October 30th, 2017. Hence, let's get straight to it.
Package Attributes
In OneSpan Sign, you have the ability to add custom data to a transaction. This data you inject in the transaction is not interpreted by OneSpan Sign. Hence you are free to store and interpret whatever data you want. In other words, this data is not visible anywhere during signing of the documents. If you have a use case where you need certain transactions to be processed for future assessment from a third party individual, you can add a "flag" to these transactions, which can be subsequently be processed by your application. Link to Post
OneSpan Sign Watermarks
Elsewhere, you've probably noticed that when signing documents in OneSpan Sign, a watermark is automatically stamped on each signature. You can have this feature turned off through support. However, the "e" logo can't be changed with your own.
Automatic Switch Between Signers
Finally, when you have multiple signers/recipients in a transaction, you can leverage the Event Notifier to automatically switch between signing sessions. Essentially, your application will need to listen for the "SIGNER_COMPLETE" event. Once that happens, it is your queue to create a new signer authentication token and build the URL of the signing session to be embedded in the src of your iframe. 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.
