Validation Error When Using Radio Buttons
Wednesday, November 22, 2023 at 11:59amI am running into an issue with my radio button group. I have selected one of the required options but when I try to complete signing I get an error that says "Not all approvals have been confirmed" I have attached a screenshot. Here is my JSON:
{
"roles": [
{
"id": "Signer1",
"type": "SIGNER",
"signers": [
{
"firstName": "Mad",
"lastName": "Hatter",
"email": [email protected]
}
]
},
{
"id": "Sender1",
"type": "SIGNER",
"signers": [
{
"firstName": "Arise",
"lastName": "Arise",
"email": xx@axxe.com
}
]
}
],
"documents": [
{
"approvals": [
{
"role": "Signer1",
"fields": [
{
"id": "signer1_group1_ccorp",
"name": "signer1_group1_ccorp ",
"type": "INPUT",
"subtype": "RADIO",
"page": 0,
"height": 10,
"width": 10,
"left": 265,
"top": 183,
"validation": {
"required": true,
"enum": [
"Tax Classification"
]
}
},
{
"id": "signer1_group1_scorp",
"name": "signer1_group1_scorp ",
"type": "INPUT",
"value": "",
"subtype": "RADIO",
"page": 0,
"height": 10,
"width": 10,
"left": 347,
"top": 183,
"validation": {
"required": true,
"enum": [
"Tax Classification"
]
}
}
]
}
],
"extract": true,
"extractionTypes": [
"TEXT_TAGS"
],
"name": "05_MadHatter_ESD_2023-11-20.pdf"
}
],
"settings": {
"ceremony": {
"extractTextTags": true
}
},
"name": "05_MadHatter_ESD_2023-11-20.pdfpackage",
"type": "PACKAGE",
"description": "NewPackage",
"autoComplete": true,
"status": "DRAFT"
}
Any ideas on what is wrong? If I set this up in the application it works perfectly. Only when using the API are we running into this issue.
Reply to: Validation Error When Using Radio Buttons
Wednesday, November 22, 2023 at 04:10pmHi Neal,
If there's no sensitive information, can you also share the PDF to [email protected]?
For the first glance, it looks like you are using text tags and x/y coordinates together. Any specific reason why not add the radio buttons using text tags like below?
{{esl_optionA:Signer1:Radio:Group("Frequency"),Value("X"),size(10,10),offset(40,-8)}}
If you still want to use two features together, I would suggest a two step approach where you uploaded the document with text tags first, then add these two radio buttons to the signature.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Validation Error When Using Radio Buttons
Monday, November 27, 2023 at 09:56amHi Neal,
Thanks for the sharing! Attached is a screenshot of the signature box, could you elaborate a bit about how you are placing this signature? It looks like position extraction to me? But I didn't see it in your JSON.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Validation Error When Using Radio Buttons
Monday, November 27, 2023 at 11:02amHey Duo,
Those are Conga Composer tags. We are passing in the signature text tag as a field in our JSON when we merge the document using the composer API. The reason we have to do this way is because the onespan tags have the same {{ }} syntax as composer mergefields. If we leave the tags as text in the document Composer removes them because it doesn't recognize them.
Do you think if we instead placed the signature tags using coordinates and removed the text tag extraction entirely it could help with the radio button validation error?
Reply to: Validation Error When Using Radio Buttons
Monday, November 27, 2023 at 11:10amHi Neal,
I think to leverage text tags is a good idea and especially when Conga Composer has the ability to inject tags. Can you also inject the text tags for the radio buttons like below?
{{esl_optionA:Signer1:Radio:Group("Frequency"),Value("X"),size(10,10),offset(40,-8)}}
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Validation Error When Using Radio Buttons
Monday, November 27, 2023 at 11:13amHi Duo, we have a requirement that both the radio buttons have no value when the document is opened to sign, since this is a tax document we need to force the recipient to make a selection. Will removing the value("X") be an issue?
Reply to: Validation Error When Using Radio Buttons
Monday, November 27, 2023 at 11:15amI see. No, it should be fine without the value("X") attribute.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer