Skipping All Optional Signatures Returning Completed Status

Hi Tracy,

Thanks for your post!

Given the background information, I would suggest to leverage the Conditional Field feature (Dev Blog Part 1, Part 2, Part 3) and use UI components like check box group to control the properties of the signatures. 

Take the attached screenshot for example, I have a check box group which requires at least one option get selected. 

During the signing, selecting each checkbox will enable the corresponding signature and mark the signature as required. This ensures signer won't be able to finish signing without selecting and signing at least one of the checkboxes and the signatures.

Duo

I have made a template to make the first signature capture mandatory for each signer then the rest optional with conditional logic to make the mandatory capture optional once any of the others are signed. 

a_2.png

b_2.png

However, in our implementation we use text tags and the Java OneSpan SDK. I can see from the SDK the conditions which I would need to create.

Example text tags for one Signer  

{{esl:Signer1:capture}}

{{?esl:Signer1:capture}}

{{?esl:Signer1:capture}}

c_2.png

It seems the action in the conditional logic uses the ID the capture field but don’t see how get from within the package object. Under the signature objects the fields are an empty list.

d_2.png

I was thinking was I could make the package as a draft then get the list of capture field id’s to add the conditions too. Is this possible or is possible to assign an id to a text tag then create the conditions upon package creation with the  .withconditions property?