Release notes and documentation for Forms 13.1.

10/umbraco-forms/developer/configuration/README.md

@@ -110,7 +110,7 @@ For illustration purposes, the following structure represents the full set of op
       "Recaptcha3": {
         "SiteKey": "",
         "PrivateKey": "",
-        "Domain": "www.google.com"
+        "Domain": "Google"
       },
       "RichText": {
         "DataTypeId": "ca90c950-0aff-4e72-b976-a30b1ac57dad"
@@ -478,7 +478,7 @@ You can obtain both of these values after signing up to create a ReCaptcha key h
 
 This setting defines the domain from which the client-side assets for using the reCAPTCHA service are requested.
 
-Valid options are `www.google.com` (the default) or `www.recaptcha.net`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies).
+Valid options are `Google` (the default) or `Recaptcha`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies).
 
 ### Rich text field type configuration
 

12/umbraco-forms/developer/configuration/README.md

@@ -111,7 +111,7 @@ For illustration purposes, the following structure represents the full set of op
       "Recaptcha3": {
         "SiteKey": "",
         "PrivateKey": "",
-        "Domain": "www.google.com"
+        "Domain": "Google"
       },
       "RichText": {
         "DataTypeId": "ca90c950-0aff-4e72-b976-a30b1ac57dad"
@@ -491,7 +491,7 @@ You can obtain both of these values after signing up to create a ReCaptcha key h
 
 This setting defines the domain from which the client-side assets for using the reCAPTCHA service are requested.
 
-Valid options are `www.google.com` (the default) or `www.recaptcha.net`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies).
+Valid options are `Google` (the default) or `Recaptcha`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies).
 
 ### Rich text field type configuration
 

13/umbraco-forms/developer/configuration/README.md

@@ -67,7 +67,8 @@ For illustration purposes, the following structure represents the full set of op
         "FieldTypes": {},
         "PrevalueSourceTypes": {},
         "WorkflowTypes": {},
-      }
+      },
+      "MandatoryFieldsetLegends": false
     },
     "Options": {
       "IgnoreWorkFlowsOnEdit": "True",
@@ -111,7 +112,8 @@ For illustration purposes, the following structure represents the full set of op
       "Recaptcha3": {
         "SiteKey": "",
         "PrivateKey": "",
-        "Domain": "www.google.com"
+        "Domain": "Google",
+        "VerificationUrl": "https://www.google.com/recaptcha/api/siteverify"
       },
       "RichText": {
         "DataTypeId": "ca90c950-0aff-4e72-b976-a30b1ac57dad"
@@ -223,6 +225,12 @@ Take care to not hide any settings that are required for the particular field or
 
 The default value and read-only settings apply to most setting types. There is an exception for complex ones where a default string value isn't appropriate. An example of one of these is the field mapper used in the "Send to URL" workflow.
 
+### MandatoryFieldsetLegends
+
+When creating a form with Umbraco Forms, adding captions to the groups for fields is optional. To follow accessibility best practices, these fields should be completed. When they are, the group of fields are presented within a `<fieldset>` element that has a populated `<legend>`.
+
+If you want to ensure form creators always have to provide a caption, you can set the value of this setting to `true`.
+
 ### Form default settings configuration
 
 The following configured values are applied to all forms as they are created. They can then be amended on a per-form basis via the Umbraco backoffice.
@@ -491,7 +499,13 @@ You can obtain both of these values after signing up to create a ReCaptcha key h
 
 This setting defines the domain from which the client-side assets for using the reCAPTCHA service are requested.
 
-Valid options are `www.google.com` (the default) or `www.recaptcha.net`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies).
+Valid options are `Google` (the default) or `Recaptcha`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies).
+
+#### VerificationUrl
+
+By default, the server-side validation of the reCAPTCHA response is sent to Google's servers at `https://www.google.com/recaptcha/api/siteverify`.
+
+Some customers with a locked-down production environment cannot configure the firewall to allow these requests and instead use a proxy server. They can use this setting to configure the URL to their proxy server, which will relay the request to and response from Google.
 
 ### Rich text field type configuration
 

13/umbraco-forms/developer/webhooks.md

@@ -0,0 +1,24 @@
+# Webhooks
+
+Umbraco Forms will register events for workflow operations that you can use with [Umbraco webhooks](https://docs.umbraco.com/umbraco-cms/reference/webhooks).
+
+Workflows are operations that you can associate with form submission, approval, or rejection actions. You can use these where you need to notify external systems of the success or failure of a workflow.
+
+On the Umbraco **Settings** > **Webhooks** dashboard, you can configure webhooks to respond to workflows.
+
+![Webhook events](./images/wehbook-events.png)
+
+You can amend the registration of workflow events in code.
+
+To remove the webhooks that are added by default you can use a composer as follows:
+
+```csharp
+using Umbraco.Cms.Core.Composing;
+using Umbraco.Forms.Core.Extensions;
+
+internal sealed class TestComposer : IComposer
+{
+    public void Compose(IUmbracoBuilder builder)
+        => builder.WebhookEvents().AddForms(formsBuilder => formsBuilder.RemoveDefault());
+}
+```

13/umbraco-forms/release-notes.md

@@ -17,6 +17,25 @@ If you are upgrading to a new major version, you can find information about the
 
 This section contains the release notes for Umbraco Forms 13 including all changes for this version.
 
+#### [**13.1.0**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.1.0) **(March 5th 2024)**
+
+With the introduction of webhooks in Umbraco 13, we've made an update to Forms to allow workflow execution events to trigger webhooks. Workflows are operations that you can associate with form submission, approval, or rejection actions. You can use these where you need to notify external systems of the success or failure of a workflow. Read more on [Umbraco Forms Wehbooks](./developer/webhooks.md).
+
+We've added an update that will help customers using Forms within locked down production environments.
+
+And there are a couple of further additions to improve the performance and accessibility of the product.
+
+**Features implemented and issues resolved in 13.1.0**
+
+* Added wehbooks for workflow execution events [#1151](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1151).
+* Added support for a proxied request when using reCAPTCHA 3 [#1159](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1159).
+* Added a configurable option to ensure accessibility requirements with regard to fieldsets are adhered to [#1163](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1163).
+    * Read more about this configuration setting [here](./developer/configuration/README.md#mandatoryfieldsetlegends).
+* Added a cachebuster querystring based on the current product version to rendered script dependencies [#773](https://github.com/umbraco/Umbraco.Forms.Issues/issues/773).
+* Ensured that client-side conditions logic correctly implements "is" with multiple values, such that the condition passes if one and only one matching value is found [#1173](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1173).
+* Fixed closing of theme picker dialog [#1174](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1174).
+* Fixed rendering of translated dictionary items used for form captions [#1175](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1175).
+
 #### [**13.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.0.2) **(February 20th 2024)**
 
 * Ensured UI for the upload of a text file for a prevalue source only allows the selection of expected .txt files.