Features can be created with illegal null values about crowdsource-reporter

[CTLocalGovTeam]

@allisonmuise

Geoform has multiple field level validations. All these validations are done at the click of the submit button. No validations are performed on focus out except for domain value fields. This is as implemented in the geoform. If you want to change this we can implement it after minimum ship.

However, just wanted to bring to your notice that, if we disable the submit button till all mandatory fields are filled, user will have no clue why the submit button is not enabled. This is more relevant in case of forms with lot of fields and scrolling.

[CTLocalGovTeam]

@allisonmuise, As discussed during the meeting last week, we are awaiting your feedback on this.

[allisonmuise]

Sorry! Thanks for the reminder.

I can continue to reproduce this issue with text fields, and to some extent with date fields, but it appears that this is a limitation of AGOL as I can reproduce this behavior with editing through the map both on production and in devext.

The behaviors I am seeing are:

• Required (aka not nullable) text fields are permitted to be null.
• Required date fields are auto-populated with 12/29/1899 on feature creation.

Let's leave these behaviors as they are for the Beta release and, if it's an issue for users, drive this change into core rather than handling it in the app.

cc: @ScottOppmann @LindsayThomas