CiviForm simplifies the application process for government benefits programs by re-using applicant data for multiple benefits applications. It's being developed by Google.org and Exygy, in collaboration with the City of Seattle and community contributors.
Is your feature request related to a problem? Please describe.
When answering a question with constraints (e.g. an enumerator question that allows up to 3 answers), the applicant has no way to know there is a constraint unless they violate it and try to submit. This can waste applicant time and be frustrating.
Example of current behavior (after clicking "Save and next") with a number question limited to 1-10:
Describe the solution you'd like.
The applicant UI should show question constraints proactively so that the applicant is aware of them up front.
What priority is this?
Probably a medium-low priority because it's just a frustration/usability issue, not a functional blocker, but it also should be a small-ish effort to fix so it might be worth considering in the northstar work.
Additional context
We considered adding this for the enumerator limits but skipped it for consistency, and we plan to add it for multiple file uploads, so it would be good to be consistent across all questions.
Here are all the questions that have this type of constraint:
Is your feature request related to a problem? Please describe.
When answering a question with constraints (e.g. an enumerator question that allows up to 3 answers), the applicant has no way to know there is a constraint unless they violate it and try to submit. This can waste applicant time and be frustrating.
Example of current behavior (after clicking "Save and next") with a number question limited to 1-10:
Describe the solution you'd like.
The applicant UI should show question constraints proactively so that the applicant is aware of them up front.
What priority is this?
Probably a medium-low priority because it's just a frustration/usability issue, not a functional blocker, but it also should be a small-ish effort to fix so it might be worth considering in the northstar work.
Additional context
We considered adding this for the enumerator limits but skipped it for consistency, and we plan to add it for multiple file uploads, so it would be good to be consistent across all questions.
Here are all the questions that have this type of constraint: