Ryan_Coleman

Change to Radio Buttons?

0 votes
Guys, Was there a change to how radio buttons are being sent? For some reason I am seeing an issue where it appears all of my radio buttons are being sent as the same group and when I try to pull the package information from the GET API call, they are not in the package. Everything else as far as signatures, labels, inputs, etc are working. Here is a snippet of what I am sending for the RADIO button. { "id": "Standard-Borrower_borrower_1_Radio1", "name": "Standard-Borrower_borrower_1_Radio1", "binding": null, "page": 0, "top": 222.20000000000016, "subtype": "RADIO", "height": 15.510000000000002, "left": 96.0, "width": 14.4599609375, "type": "INPUT", "value": null, "validation": { "required": true, "maxLength": null, "errorCode": null, "minLength": null, "errorMessage": null, "pattern": null, "eNum": [ "Standard-Borrower_borrower_1_1" ] } } UPDATE: After doing some extensive testing, I've found the following results. 1. If this is a new package and this is sent via the create transaction POST API call the documents with radio buttons work as intended. 2. If this is not a new package and document is added via the POST /packages/{packageID}/documents API call they do not work properly. It appears that they are all grouped together which causes an error on our documents.

Approved Answer

Reply to: Change to Radio Buttons?

1 votes
Duo, So after doing more research in exactly what I'm sending, the value "enum" is a reserved keyword in C# so I wasn't able to use that as a property. In the add method, I am taking the JSON package and doing a quick rename but that same step wasn't happening in the add document method. I added that portion and now am able to get the correct grouping for my radio buttons. Thanks for the help!!

Reply to: Change to Radio Buttons?

0 votes
Hi Ryan, Have you added "Accept: application/json; esl-api-version=11.21"(version doesn't matter) in your request header? It's mentioned in 10.6.1 release note that API calls need to add "esl-api-version=xxx" in order to retrieve all fields. Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Change to Radio Buttons?

0 votes
Duo - I did not see that and when I added it to my GET packages API call, I was then able to see the radio buttons in the returned JSON. That's good to know. I did update my post around the same time you replied so I am not sure if you saw the additional information I posted. Apparently my problem is with the addition of the radio button fields to an existing package.

Reply to: Change to Radio Buttons?

0 votes
Hey Ryan, Can you provide me with two package IDs that one is expected and one is undesired, so that I can reproduce the exact scenario? Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Change to Radio Buttons?

0 votes
Duo, Look at this package. azUy3JR10XYGLNLukONM_bOnQSM= There are two documents that are exactly the same. The first document was sent up with I created the transaction. It works. The second document, the one with the _01, does not work and it was sent via the add documents post api. If you do a get on that package, you'll see that there are differences in the enum between the documents and the "_01" document doesn't have any of the radio buttons grouped.

Reply to: Change to Radio Buttons?

0 votes
Hi Ryan, The _01(bad one) document's four radio buttons lost their enum information, that's why they are considered as in the same group. I tried in Postman, to first create a package with one document, then upload another document with same payload, but it works properly at my side. One small issue I found is that your sender seems to have an empty first name? But this may not related to your issue. Do you have Fiddler installed at your machine or can you print out the request payload you've sent out to see whether the enum information is carried? Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Change to Radio Buttons?

0 votes
Duo, I agree, it appears that the grouping is not being carried over. This functionality worked the last time I tested it but I cannot honestly say when that was. Maybe 4 to 5 months ago at the earliest. Here is what was sent up when I created the _01 document. { "approvals": [ { "id": "Approval_1", "fields": [ { "id": "Date_0147c56a-cd7f-4b81-bcdd-f7752245e6f1", "binding": null, "page": 0, "top": 700.13860015869113, "subtype": "LABEL", "height": 31.020000000000003, "left": 632.98820190429717, "width": 103.35888671875, "type": "INPUT", "value": "08/23/2019", "validation": null }, { "id": "3bde392e-d61a-4184-a545-976b7389e6ba", "binding": null, "page": 0, "top": 698.83860015869118, "subtype": "FULLNAME", "height": 31.020000000000003, "left": 151.8841995239257, "width": 227.576171875, "type": "SIGNATURE", "value": null, "validation": null }, { "id": "input_803c5751-67a3-4d1d-9e76-f49b7ed8e22c", "binding": null, "page": 0, "top": 262.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_5cf698c3-b842-466e-8bed-b00cd3676bcb", "binding": null, "page": 0, "top": 288.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_705230ff-2c0e-4713-a278-c4ee604b6908", "binding": null, "page": 0, "top": 314.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_68853e9b-a1df-4cf7-a0b6-bf1a65b0c505", "binding": null, "page": 0, "top": 340.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_62ee5624-5c60-42bd-8558-e37fc039446d", "binding": null, "page": 0, "top": 366.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_2078a2f7-69b3-41ec-88bc-f7fb373b4c83", "binding": null, "page": 0, "top": 509.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_7897dcbc-b782-4557-af06-2bfe3571038e", "binding": null, "page": 0, "top": 535.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_f35abb34-91ba-47d5-83c3-338d3edaa9e5", "binding": null, "page": 0, "top": 561.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_6ab26720-3463-4f08-bf74-1382065c8c01", "binding": null, "page": 0, "top": 587.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "input_8410ffb3-9ef8-4de2-9a06-64b0cd1a2803", "binding": null, "page": 0, "top": 613.40000000000009, "subtype": "TEXTFIELD", "height": 11.88, "left": 91.0, "width": 587.80615234375, "type": "INPUT", "value": null, "validation": null }, { "id": "Standard-Borrower_borrower_1_Radio1", "name": "Standard-Borrower_borrower_1_Radio1", "binding": null, "page": 0, "top": 222.20000000000016, "subtype": "RADIO", "height": 15.510000000000002, "left": 96.0, "width": 14.4599609375, "type": "INPUT", "value": null, "validation": { "required": true, "maxLength": null, "errorCode": null, "minLength": null, "errorMessage": null, "pattern": null, "eNum": [ "Standard-Borrower_borrower_1_1" ] } }, { "id": "Standard-Borrower_borrower_1_Radio2", "name": "Standard-Borrower_borrower_1_Radio2", "binding": null, "page": 0, "top": 222.20000000000016, "subtype": "RADIO", "height": 15.510000000000002, "left": 167.5, "width": 14.4599609375, "type": "INPUT", "value": null, "validation": { "required": true, "maxLength": null, "errorCode": null, "minLength": null, "errorMessage": null, "pattern": null, "eNum": [ "Standard-Borrower_borrower_1_1" ] } }, { "id": "Standard-Borrower_borrower_1_Radio3", "name": "Standard-Borrower_borrower_1_Radio3", "binding": null, "page": 0, "top": 465.30000000000007, "subtype": "RADIO", "height": 15.510000000000002, "left": 96.0, "width": 14.4599609375, "type": "INPUT", "value": null, "validation": { "required": true, "maxLength": null, "errorCode": null, "minLength": null, "errorMessage": null, "pattern": null, "eNum": [ "Standard-Borrower_borrower_1_2" ] } }, { "id": "Standard-Borrower_borrower_1_Radio4", "name": "Standard-Borrower_borrower_1_Radio4", "binding": null, "page": 0, "top": 465.30000000000007, "subtype": "RADIO", "height": 15.510000000000002, "left": 167.5, "width": 14.4599609375, "type": "INPUT", "value": null, "validation": { "required": true, "maxLength": null, "errorCode": null, "minLength": null, "errorMessage": null, "pattern": null, "eNum": [ "Standard-Borrower_borrower_1_2" ] } } ], "role": "Role1", "accepted": null, "signed": null }, { "id": "Approval_2", "fields": [ { "id": "Date_76d63c47-601b-4fdd-b020-b0ce40e8d0c8", "binding": null, "page": 0, "top": 769.05159301757794, "subtype": "LABEL", "height": 31.020000000000003, "left": 632.98820190429717, "width": 103.35888671875, "type": "INPUT", "value": "08/23/2019", "validation": null }, { "id": "f49c8af5-50bc-4545-a1ca-8e92e897064c", "binding": null, "page": 0, "top": 767.751593017578, "subtype": "FULLNAME", "height": 31.020000000000003, "left": 151.8841995239257, "width": 227.576171875, "type": "SIGNATURE", "value": null, "validation": null } ], "role": "Role2", "accepted": null, "signed": null } ], "id": "Standard_Borrower_01", "index": 1, "name": "Standard Borrower_01", "isConsent": false }

Reply to: Change to Radio Buttons?

0 votes
Good finding and glad to hear you've solved it so quickly! Just want to share with you that, I encountered a similar issue when building JSON in Apex language. I/our Apex SDK had to add an "_x" at the end for the property then replaced all when sending out. Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off