Numbers: Limit Input
Need to set max first if min is going to be higher than default.
Consider changing from 150>150 to 1994>2018 for years.
To set the min to 1994, the max needs to be set to something higher. Try 9999 just as a placeholder.
Now to set the max, while entering 2018 it resets on changing the 9999 to 2 because 2 is less than 1994. Either enter 1994 and use the control to increment up, or change to 2999 and then insert as 2018999, then remove the trailing 999.
In summary, we really just need to enter the max before the min.
2) Numbers: Conditional logic
Need to check relation of field 2 to field 1. Example:
If field 1 is a start year then field 2 must be >= field1.
3) Conditional logic: It would be helpful to be able to reference a field name by an ID other than the label. Otherwise we need to ensure every field has a unique text label, which often isn’t necessary. Field names similar to this are available in email handling via “Add form data”. It would be helpful to see those names for this purpose in the field editor and the conditional logic dropdown next to the field label. This way we’ll know the ID for a field as we go into conditional logic to set rules based on that field.
4): Each field has a required flag. But a field may only be required if conditionally it must be displayed. For example, the user checked Yes to “there is an emergency phone#”, or similar. If they checked that, then the phone is required, otherwise not.
#6a: Consider a multi-use form, like “things I did today”. How do we allow a user to see previously submitted forms? And how do we allow them to edit a specific instance of a previously submitted form.
#6b: Related: We should be able to get a unique form submission ID that we can return via email to the user. This will be used for subsequent enquiries.