Confirm Password field in Umbraco Forms

[bdarmanin]

A brief description of your feature request goes here.

We would like to have the option to add the confirm password field in umbraco forms for new members signup

[nul800sebastiaan]

Thanks for your feature request. We're working on fixing bugs for the foreseeable future, but we'll put this on the list for when we are ready to work on new field types.

For now, you can implement your own custom field type to achieve this functionality. https://our.umbraco.com/documentation/Add-ons/UmbracoForms/Developer/Extending/Adding-a-Fieldtype

[markadrake]

Umbraco.Forms could benefit from some additional complexity that is generic enough to solve the "password confirmation" UX flow above—and more.

1. Use tabs here to contextually group settings/configuration.

I don't want to rekindle the great tabs debate, but I think the form being used to configure questions is growing too long. I like to use tabs to contextually group fields to address specific domains. There are clearly three domains when it comes to questions, and if we were to follow the convention in the CMS we could easily allow developers to add more to them.

I don't know if the convention would be to use tabs or apps. Apps have the advantage of a clear extension point elsewhere in the CMS, but aren't typically used to edit data attached to the current record.

1. Question
2. Validation
3. Conditions

Today	With Tabs	With Apps

2. Provide rulesets under validation.

Follow the UI and UX convention for conditions for validation. This would allow us to create more robust rulesets for validation. This would allow for custom complexity such as:

• If password is not empty,
  • password confirmation is required (AND)
  • password confirmation must match password

I had some additional feedback to share but this may not be the place to post it.