- Issue created by @goose2000
Normally, a Boolean field when set to required shows no "N/A" option. Good and normal. When you create conditions that make a previously unseen and not required Boolean to, seen and now required, a UI issue arises where the "N/A" option still persists as though it was a not required Boolean field. Below you can see "What is your employment status has triggered the subsequent Boolean field which is required. You can also notice two * * required stars appear.
Create a conditional that produces a Boolean field to appear and be required. Set this to display with radio buttons.
View and trigger the condition in the form.
I think this issue may require extra steps to remove the "N/A" option if it can't be caught earlier. Instinct tells me, it's already there as not required, but the switch to required, does not clean-up the options.
Active
4.0
Code