gberde's account

Thanks for the quick response! Is "signature" and "approval" the same? If yes, then your assumption is correct - all labels and checkboxes are associated to one approval.

Questions - 

*. Before step 1, we have entire template json (because we call `Search` endpoint before clone). Can we use the approval Json in CLONE call to remove checkboxes that we don't need? 

*. question about step 4 in your description - Does OneSpan retain the same approval id - sNUh3eWKOvoY  ?

And just to confirm - in step 1, we need to Clone package in "Draft" status to be able to run thru the flow, correct?

I tested the solution.. but we are losing "Conditions" (conditional logics in template). How do we retain conditions in Step 4 of your flow ?

Doesn't `Clone` endpoint honor `validation >> disabled` ? 

I am sending `value` of field nodes in my clone call (higlighted in bold) which is honored and reflected on my package.

here's what I send in my clone call -

•  
• {
•     "name": "Template Form",
•     "data": {
•         "senderVisible": false
•     },
•     "description": "Some description",
•     "type": "PACKAGE",
•     "visibility": "ACCOUNT",
•     "status": "SENT",
•     "emailMessage": "This is a package level email message.",
•     "roles": [
•         {
•             "id": "<roleGuid>",
•             "specialTypes": [],
•             "attachmentRequirements": [],
•             "data": null,
•             "reassign": false,
•             "emailMessage": {
•                 "content": "Please sign this Form"
•             },
•             "type": "SIGNER",
•             "index": 0,
•             "signers": [
•                 {
•                     "address": {
•                         "state": "TX",
•                         "country": "USA",
•                         "city": "Austin",
•                         "address1": "",
•                         "address2": "",
•                         "zipcode": ""
•                     },
•                     "company": "",
•                     "timezoneId": "",
•                     "email": "[email protected]",
•                     "external": null,
•                     "firstName": "John",
•                     "language": "",
•                     "lastName": "Owner",
•                     "phone": "+xxxx",
•                     "professionalIdentityFields": [],
•                     "signature": null,
•                     "title": null,
•                     "userCustomFields": [],
•                     "specialTypes": [],
•                     "passwordTimestamp": null,
•                     "idvAuthentication": null,
•                     "group": null,
•                     "knowledgeBasedAuthentication": null,
•                     "name": "",
•                     "auth": {
•                         "scheme": "NONE",
•                         "challenges": [
•                             {
•                                 "question": "+xxxx"
•                             }
•                         ]
•                     }
•                 }
•             ],
•             "name": "AdminSigner"
•         }
•     ],
•     "documents": [
•         {
•             "id": "default-consent"
•         },
•         {
•             "id": "32c24ac850fdeacf294689d14228808f9467c952348c41fe",
•             "approvals": [
•                 {
•                     "id": "3cblB0flwCYN",
•                     "fields": [
•                         {
•                             "id": "55ArymjQxDQT",
•                             "name": "Title",
•                             "value": "Admin Sr"
•                         },
•                         {
•                             "id": "K6pJVOheUzEG",
•                             "name": "PhoneNumber",
•                             "value": "xxxx"
•                         }
•                     ]
•                 }
•             ]
•         }
•     ]
• }

This is the block of "Clone" payload I am referring to - 

"auth": { "scheme": "SMS", "challenges": [ { "question": "1NNNNNNNNN" } ] }