Please make field constraints required to be "saved"
When you create a field constraint, and leave the screen, the field constraint will save, but will not included updated changes.
Example:
Field "Do you like to eat pizza" is set to only appear for the HoH for the program.
When creating the constraint you set it to "is HoH (program) =yes" and leave the screen to complete another task.
It looks like the screen is saved, but the constraint is still operating at "is HoH (program)"=no since "save" was not pressed after updating the field to "is HoH (program)"=yes.
Even though HoH is set to =yes, it was never saved and still operates as a no, meaning all other HH members will have the question displayed. The UI will show HoH =yes and it is confusing, because you believe the field constraint is correctly set up.
Can we make "saving" constraints a requirement?
As part of our ongoing efforts to build the best feedback platform for you, ideas that have not received a vote or comment in the past year have been set as “Archived.” Please feel free to resubmit this idea using this submission guide.