Ignore required fields on conditionally hidden pages
If an entire page is hidden, it makes logical sense that the fields on their marked as required are not in fact required to be completed since the user can not access them at all.
I recently learned we have to add a condition to every required field on a potentially hidden page to honor the same formula as the one being determined to hide the page in the first place.
This is highly inefficient and unpractical to maintain on a consistent and scalable basis since many of those required fields are conditionally required already based on field results on their same page.
Hidden pages should not prevent a user from submitting a form, regardless of the fields on them and their visibility/requirement logic.
I would hope this is a simple fix in the form completion validation occurring on the back end.
James P.
shared this idea
-
Kayla Anderson
commented
Our forms contain many pages that are shown or hidden based on the user’s selections. Sometimes a user starts a form with one selection, then switches to a different version. If they don’t manually clear the data on the now-hidden pages, they can receive an error that a required field is missing, because their earlier input triggered a requirement on a field they can no longer see.
To prevent confusion, we need one of two solutions:
Automatically clear data on any page when it becomes hidden, or
Ensure that hidden fields are never treated as required.
Either option would eliminate errors caused by hidden fields.