OneSpan Sign Developer Community: Week in Review (June 19, 2017)
Let's take a quick look at what happened for the week of June 19th in the OneSpan Sign Developer Community.
How Frequently Can You Call OneSpan Sign?
Right now, we do not impose any limit on how many API calls you can make to OneSpan Sign per given time frame. However though, if you do end up putting a huge strain on our servers, you will risk having your account blacklisted as we do monitor the number of calls hitting our servers. Link to Post
Custom Field Description
In OneSpan Sign you have the ability to add custom fields. A custom field is one that, at the time of signing, is automatically populated with data specific to the signer/recipient. In addition, you can add a description to each custom fields. However, once you've placed a custom field and you hover over it, the description is not going to appear in the tooltip text. Unfortunately, this is the current behavior in OneSpan Sign and is consistent across both the classic and new user interface. Link to Post
Editing Transactions
Once a transaction has been sent for signing and you wish to make some edits on it, you can do so by changing the transaction status back to DRAFT. However, if a transaction is completed, then you will not have the ability to make any edits on the transaction. In this case, you will need to disable the auto-complete feature that is on by default. By doing so, you will have a chance to review the transaction and make some changes. 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.
