Allowing More Variety of Comparison in Conditional Docouments

[bowenng]

Conditional documents is a helpful feature to optionally exclude forms without duplicating templates. However, the logic allowed to filter out forms seem to be limited. For example, it'll be nice to allow inequality or string check for number fields and text fields as opposed to only allowing checking for emptiness.

[omohokcoj]

Hi @bowenng for exact string match it's possible to use "select" field type with options in the condition.
Regarding the number field - could you please provide an example of your use case where additional conditions are required?

[bowenng]

Thanks, @omohokcoj. For the number field, examples would be like "if the applicant make < $XXX amount for a given year, the applicant needs to fill in this additional form."

For my use case, is it possible to achieve it with some custom logic? As far as I know, it might be difficult because once a submission is created, I can't add or remove forms. In my workload, I have a dozens of forms to fill and depending on the results of earlier forms, some forms are not needed.

[bowenng]

Similar to https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocuments/update/

[omohokcoj]

@bowenng it might be possible to achieve this with conditional documents and checkboxes/boolean values sent to the API to show/hide certain documents based on your application logic:
https://www.docuseal.com/resources/add-conditional-documents - for instance "applicant_more_than_10k" field can be set as condition on the document so that when you pre-fill it via api values: {"applicant_more_than_10k": false} the document is excluded form the submission.

[bowenng]

I see. When you say "pre-fill it via api values: {"applicant_more_than_10k": false}", do you mean to have a hidden field for my code to call the REST API to fill as kind of a hack to achieve the desired result? I'd image my service probably needs to listen to the changes happening on the form and then send requests to change this hidden field.

[bowenng]

In our manual workload currently, a lot the values are unknown until the applicant starts filling in the forms. We will send them additional forms based on the results of the previous forms. Might be hard to ask them to tell us every value that might be needed to determine if a form is needed upfront, because the decision is not flat and it's more branched.

E.g. filling in some fields on form 1 might take them to form 3 and filling in form 3 might trigger requirement for form 7 and 8. It's too much to ask them tell us about all these fields in form 1, 2, 3... 10 upfront so we can decide what forms to send you.

[omohokcoj]

@bowenng we made number field "greater" "less_than" "equal" "not_equal" conditions available in the latest version

[bowenng]

Thank you so much! Your product is amazing.