OneSpan Sign Release 11.48: No Signature Fields
OneSpan Sign version 11.48 was recently deployed to preview and sandbox environments, and the update includes new and exciting product capabilities. In the first part of this blog series, we outlined the most notable updates in the release. Picking up where we left off, we will unveil more features in this blog and explain how these solutions could empower your use cases. Let’s get started!
No Signature Fields
As a transaction sender, imagine the scenario when you are designing a document hundreds of pages long that typically requires a signature on the last page. In the previous sender experience, you would have had to scroll all the way to the bottom, place a signature, and scroll back up to finish up the rest of the design, which is tedious and time-consuming.
However, this will no longer be the case after the release 11.48, since the introduction of No Signature fields. When designing an e-transaction, senders can now add fields to a document without having added a signature block first. Once a signature block is added, all previously added fields will be attached to it. Or if you simply send the transaction without adding a signature block, the signer will still be able to fill in the fields and accept the document.
Note:
- In order to leverage No Signature fields, please contact our support team and have the feature turned on at your account.
- Once the feature has been turned on, theoretically all field types can be added without a signature, including binding fields, custom fields, and other input fields.
For Integration Users
Leveraging this feature is straightforward for UI users, and integrated users can also benefit from it. The ability to have signers fill in the fields and finish signing in an accept-only fashion gives you the potential to implement these use cases when the signer needs to be part of the signing flow, but they don’t need explicit signatures to sign.
From API modelling’s perspective, we knew that a document contains multiple approval (signature) instances, and each approval node is composed of a signature field and other types of fields. With the feature turned on, it’s now possible to create an approval without a signature field.
To give you a real example, RESTful API users can use below sample JSON to create a transaction with a no signature field:
{
"roles": [
{
"id": "Signer1",
"signers": [
{
"email": "[email protected]",
"firstName": "John",
"lastName": "Smith",
"company": "OneSpan Sign"
}
]
}
],
"documents": [
{
"approvals": [
{
"role": "Signer1",
"fields": [
{
"page": 0,
"top": 100,
"subtype": "TEXTFIELD",
"height": 50,
"left": 100,
"width": 150,
"type": "INPUT"
}
]
}
],
"name": "Document1"
}
],
"name": "No Signature Fields",
"language": "en",
"emailMessage": "",
"description": "New Package",
"autocomplete": true,
"status": "SENT"
}
Similarly, it’s also possible for SDK users to create such a transaction:
EslClient eslClient = new EslClient(API_KEY, API_URL);
DocumentPackage pkg1 = PackageBuilder.newPackageNamed("No Signature Fields " + System.currentTimeMillis())
.withSigner(SignerBuilder.newSignerWithEmail("[email protected]")
.withFirstName("John")
.withLastName("Smith")
.withCustomId("Signer1")
)
.withDocument(DocumentBuilder.newDocumentWithName("document 1")
.withId("Document1")
.fromFile("your_file_path")
.withSignature(SignatureBuilder.acceptanceFor("[email protected]")
.withField(FieldBuilder.textField().onPage(0).atPosition(200, 200).withSize(150, 50))
)
)
.build();
PackageId packageId = eslClient.createPackageOneStep(pkg1);
eslClient.sendPackage(packageId);
Conclusion
This should provide you enough information to add No Signature fields both as ad-hoc and integrated users. If you have any questions regarding this blog or anything else concerning integrating OneSpan Sign into your application, visit the Developer Community Forums. Your feedback matters to us!
