hcd-integrations's account

The above JSON payload worked. Thank you Duo. I was paring down the JSON a little too much and it needed the validation property.

"validation": {

    "group": "",

    "errorCode": null,

    "required": false,

    "maxLength": null,

    "minLength": null,

    "enum": null,

    "disabled": false,

    "minimumRequired": null,

    "maximumRequired": null,

    "errorMessage": "",

    "pattern": ""

  },

Hi Duo. So we created a JSON payload (attached) and uploaded our forms. We get a response that the package is successfully created. However, when we query the package through an API call (ex. https://sandbox.esignlive.com/api/packages/S4Yk7Df3CmNpZaGtG6WmT14gbOU=) the JSON we get back does indeed contain all the field injected values we sent, including X for the checkboxes and radio buttons. 

However, when we sign into our OneSpan sandbox and view the forms on the dashboard, they contain no field injected values. The fields are all blank. 

Thank you Duo. We are able to see the data now. Question: if we upload a PDF that has condition logic for some of the fields, will OneSpan create the template and keep that logic or do we need to add it to the JSON payload?

Yes, that's correct. Are there any examples of what that conditions node would look like in the JSON payload?

Thank you Duo. We had the samples working but now we're getting errors back such as this, even though we send one document and a very simple payload, which hasn't changed.

{"messageKey":"error.validation.documentPreVerifyInvalidResponseNumberError","parameters":{"errorException":"number of documents that need verification = 2, number of verification results = 0"},"message":"The number of Pre-Verify results does not match the number of documents that were sent for verification.","code":400,"name":"Validation Error"}