Registration Forms Required Fields

[matt1hathcock]

Registration Forms Required Fields

Description

I discovered yesterday when working with registration forms locally and reproduced today while demonstrating functionality internally. The user.email or user.username field must be included on the registration form and must be required in order to save, however neither one is configured as required by default so the form being built cannot be saved. An error message shows and you must leave the page to configure the field(s) correctly and then return to build the form again from scratch.

[robotdan]

This is working as designed as far as I know.

Scenario 1:

1. Create a new form of type registration
2. Try to save form w/out user.email or user.username fields assigned the form
3. Validation error, one or the other is required

Scenario 2:

1. Create a new form of type registration
2. Add a user.email, user.username or both to the form, but the field is marked as optional
3. Validation error, the field must be marked as required.

Is it scenario 2 that is the issue, or scenario 1? You can have one to many fields defined for user.email or user.username, some may be required and some may be optional.

So the error is correct, if you do not yet have a user.email field that is configured to be required = true, you must go create one, or add an existing field configured this way to the form.

This is the current design, do you have a preferred UX behavior you'd like to see?

[matt1hathcock]

Scenario 2 is what I ran into and had a thought that it made sense for them to be that way out of the box since either one must be configured required = true for saving. mainly because the user loses the whole form just configured in order to go make the update. Understood that this is expected behavior and easily overcome knowing this is the default state for those fields.