Logic driven registration form
There are times when an organization needs to control access to a form fields based an the preceding entry. Example -
kid's org for summer swim lessons.
Parents register kids.
Some parents want kids in swim and dive and tennis. Some parents only want swim. So, if parent selects dive let's say, then all form fields under dive section would appear. If they select "No" to dive registration section, then no need for them to see of answer dive section fields.
This will do 2 things:
1- allow for access only when the parents want to register kid for a team
2- force the parent to fill out all required fields if they want to place kid in team
without this functionality parents have to look at sections that do not pertain to them, and admin cannot set a required field in a section as this would force answer for those not interested in that activity/team/
Walt Bilofsky commented
It seems like this would greatly complicate the implementation.
But there's an easy way to get most of the benefit. Give the admin the option to hide sections of the registration form, and specify a header to click to show the section. Then you could say "Click here to register for dive," and "Click here to register for swim," etc.
Sort of the same way the WA Help pages work. They show the topics, and then you click to expand.
It wouldn't help with the required fields, but would otherwise simplify complicated registration forms, and should be much easier to implement than full logic.
Logic and conditions are is super important for great forms. Look to JotForm and the options they provide. Today, we're forced to split some of our registration forms and product purchase forms to JotForm to get the workflow we need since WA doesn't support the complexity we need.