Overview:
- What’s new in Umbraco Forms 11.2 and 10.4?
- Umbraco Forms is faster!
- Customize Default FIelds For A Form
- API Enhancements
- Additional updates and release notes
- How to get your hands on the new release
The features are available for solutions based on both CMS versions 11 and 10 and are functionally equivalent. As such if you are using Umbraco Forms for an Umbraco 11 project, you can update to Forms 11.2. If your project is running Umbraco 10, version 10.4 of Forms is available.
All new Umbraco Cloud projects will be running the latest versions of Umbraco Forms, and one-click upgrades are available for existing projects.
What’s new in Umbraco Forms 11.2 and 10.4?
This minor release is a relatively small one, focusing on performance, developer experience and aligning all versions from a functional perspective for when Forms 12 is released alongside Umbraco 12 (release candidate is already available!).
Umbraco Forms is Faster!
The new releases contain multiple optimizations and improvements that help enhance the performance of Umbraco Forms. These are mainly noticeable as an editor/administrator when working with the Forms section trees and editors, especially if you have a large number of forms.
We've also been able to reduce the number of database calls required when saving form submissions.
All in all, you should have a snappier Forms section that requires fewer resources and is better to work with.
Customize Default Fields For a Form
We have added the ability to configure what fields are added by default when creating a new form. This is an expansion of the ability added for default workflows in a previous release. The default implementation does what Forms have done previously, which is to add a single "data consent" field to a single-page form.
Details and examples for configuring default fields (and workflows) can be found in the documentation.
Headless API Enhancements
A few versions back we released an update to Forms that provided an API, allowing you to retrieve definitions and submit forms in a headless fashion. We've added a configuration option that you can use to enable or disable the API. As not everyone will want to use it, by default this is off, so you will now need to amend this configuration if you want to use the API. Please note that anyone upgrading will need to set this configuration value to continue using the API after the update. For more info see the documentation on how to enable or disable the API.
We've also included a hook for custom form validation, such that forms submitted via the API are aligned in their behavior in this respect with those submitted via standard full-page post backs. This ensures any custom validation you have applied to your Forms setup will validate a form submission.
Finally, an optional "culture" parameter can now be added to the request to receive a form definition and to post a submission. This ensures things like dictionary translations used for form labels work as you'd expect in a multi-language setup. Usage is documented here.
Tag helper, IP recording, and more…
Included in this release is an additional option for rendering forms, this time using the Tag Helper approach. Details for use, along with other improved documentation on the various options available for rendering forms, can be found here.
Umbraco Forms has traditionally recorded the IP of a form submission into the database, along with the other details provided.We've added configuration for this feature now where the default, maintains existing behaviour, and you can disable it with configuration. Note that from Umbraco Forms 12 IP recording will be disabled by default for new installations, and can be enabled with configuration. See the the configuration documentation for details.
You can find the entire list of features, improvements and fixes for both 11.2 and 10.4 in the Umbraco Forms release notes.
