Plan requirement
| Subscription | Suite Growth or higher, Support Professional or higher |
| Access | Admin |
A conditional field can be required, but only while it is visible. Understanding that rule prevents forms nobody can submit.
Make it required
- Open the form's conditions in Admin Center.
- Find the condition that shows the field.
- Mark the field as required within that condition, rather than on the field itself.
- Save and test by selecting each value of the driving field in turn.
Required on the field or in the condition
These are two different things and the difference matters.
- Required on the field applies wherever the field appears, on every form.
- Required in the condition applies only when that condition has made it visible.
Marking a conditional field as required at field level is how you produce a form that cannot be submitted: the field is required but hidden, so nobody can fill it in and nobody can see why they are blocked.
Test every branch
Conditions multiply quickly. A form with three driving values needs three tests, not one. Selecting each value and trying to submit takes two minutes and catches the case where a required field never becomes visible.
Required is a cost. Every required field on a public form loses you some proportion of people who abandon it. Requiring it for agents on solve is often enough, and does not stand between a customer and asking for help.
Comments
0 comments
Article is closed for comments.