From fbf44b4db2e1dff1b6200b2a16d4bd288429e22e Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 4 Jun 2024 12:18:52 +0200 Subject: [PATCH 01/38] Added details on SupportsHtml setting attribute property. --- 13/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 ++ 13/umbraco-forms/developer/extending/setting-types.md | 4 ++-- 14/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 ++ 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md index 424abd7abb1..a71e6c03a7e 100644 --- a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -172,6 +172,8 @@ public virtual string MySetting { get; set; } `SupportsPlaceholders` is a flag indicating whether the setting can contain ["magic string" placeholders](../magic-strings.md) and controls whether they are parsed on rendering. +`SupportsHtml` is a flag indicating whether the setting contains HTML markup. + `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). `IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. diff --git a/13/umbraco-forms/developer/extending/setting-types.md b/13/umbraco-forms/developer/extending/setting-types.md index 420a3fe59fb..78469637e70 100644 --- a/13/umbraco-forms/developer/extending/setting-types.md +++ b/13/umbraco-forms/developer/extending/setting-types.md @@ -20,11 +20,12 @@ The following setting types are available and are used for the field, prevalue s | Name | Description | Used in | |---------------------------|-------------------------------------------------------------------|-------------------------------------------------| | Checkbox | Uses a single checkbox for entry | | -| DocumentMapper | Used for selection of a documenttype | The "Save as Umbraco node" workflow | +| DocumentMapper | Used for selection of a documenttype | The "Save as Umbraco node" workflow | | Dropdownlist | Used for selection from a list of options | | | EmailTemplatePicker | Used for selection of an email template | The "Send email with Razor template" workflow | | FieldMapper | Used to map fields from a form to required aliases | The "Send to URL" workflow | | File | Used for selection of a file | The "Send email with XSLT template" workflow | +| MultipleTextString | Used multiple textboxes for multiple entries | Not used in core types | | NumericField | Uses numerical text box for entry | | | Password | Uses password text box for entry | | | PasswordNoAutocomplete | Uses password text box for entry (with autocomplete disabled) | | @@ -38,7 +39,6 @@ The following setting types are available and are used for the field, prevalue s | Textfield | Used a single-line textbox for entry | | | TextfieldNoAutocomplete | Used a single-line textbox for entry (with autocomplete disabled) | | | TextWithFieldPicker | Used a single-line textbox/form field list for entry | Not used in core types | -| MultipleTextString | Used multiple textboxes for multiple entries | Not used in core types | All of the above setting types are used in one or more field, prevalue source and workflow types available with Umbraco Forms. For the less common ones, a usage has been indicated in the table. diff --git a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md index 27d0311a728..3968fd9fee8 100644 --- a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -140,6 +140,8 @@ The `View` property indicates a property editor UI used for editing the setting `SupportsPlaceholders` is a flag indicating whether the setting can contain ["magic string" placeholders](../magic-strings.md) and controls whether they are parsed on rendering. +`SupportsHtml` is a flag indicating whether the setting contains HTML markup. + `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). `IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. From 91da8ee9ba9b81d56b5d754c6da36ad4462fe28f Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 11 Jun 2024 10:47:23 +0200 Subject: [PATCH 02/38] Added release notes for Forms 14.0.2 --- 14/umbraco-forms/release-notes.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index cb5e6780603..b2c2e01f41c 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -17,6 +17,10 @@ If you are upgrading to a new major version, you can find information about the This section contains the release notes for Umbraco Forms 14 including all changes for this version. +#### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** + +* Fixed issue with upload of text file for the prevalue source based on file contents. + #### [**14.0.1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.1) **(June 6th 2024)** * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). From 24aebc52478ce0e89de0b589c136fddf36afda92 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Fri, 21 Jun 2024 07:36:49 +0200 Subject: [PATCH 03/38] Added release notes for 13.2 and 14.1. --- 13/umbraco-forms/release-notes.md | 19 +++++++++++++++++++ 14/umbraco-forms/release-notes.md | 11 ++++++++++- 2 files changed, 29 insertions(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 448d863e8e9..169536a2bfa 100644 --- a/13/umbraco-forms/release-notes.md +++ b/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.2.0**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(TBC)** + +* Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) +* Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) +* Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) +* Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) +* Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) +* Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230) +* Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). +* Resolved duplicate approval occurring when record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). +* Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220) +* Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219) +* Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214) +* Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206) +* Added setting option for the "send to URL" workflow to switch between caption and alias for the field value's XML element [#1202](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1202) +* Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) +* Restored target used to generate local configuration schema information [#1226](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1226). +* Fixed issues with retrieving fields and assigning default values when using the datasource wizard + #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** * Corrected alignment of label `for` and input `id` attributes in the date picker field [#1200](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1200). diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index b2c2e01f41c..4cde0105f1a 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -17,6 +17,15 @@ If you are upgrading to a new major version, you can find information about the This section contains the release notes for Umbraco Forms 14 including all changes for this version. +#### [**14.1.0**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) **(TBC)** + +* Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) +* Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) +* Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) +* Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) +* Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) +* Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) + #### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** * Fixed issue with upload of text file for the prevalue source based on file contents. @@ -25,7 +34,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). * Restored target used to generate local configuration schema information [#1226](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1226). -* Resolved duplicate approval occuring when record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). +* Resolved duplicate approval occurring when record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). * Added some missing localization keys and translations. * Fixed description of management API on Swagger UI. * Fixed display of specific form access list for user and group security. From afd0d6f77a60c9397825b9a174508d4daae2df3f Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Fri, 21 Jun 2024 07:44:41 +0200 Subject: [PATCH 04/38] Added details of additional placeholder format functions. --- 13/umbraco-forms/developer/magic-strings.md | 23 ++++++++++++--------- 14/umbraco-forms/developer/magic-strings.md | 22 +++++++++++--------- 2 files changed, 25 insertions(+), 20 deletions(-) diff --git a/13/umbraco-forms/developer/magic-strings.md b/13/umbraco-forms/developer/magic-strings.md index 4ab8372d881..7e9b174f5b6 100644 --- a/13/umbraco-forms/developer/magic-strings.md +++ b/13/umbraco-forms/developer/magic-strings.md @@ -82,16 +82,19 @@ For example, to truncate a string value read from an Umbraco page field with ali Umbraco Forms ships with the following filters: -| Filter | Function | Arguments | Example | -| ----------------------------- | ---------- | -------------------- | ------------------------------------ | -| Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | -| Convert string to lower case | `lower` | | `[#field \| lower]` | -| Convert string to upper case | `upper` | | `[#field \| upper]` | -| Truncate a string | `truncate` | number of characters | `[#field \| truncate: 10]` | -| Format a number | `number` | format string | `[#field \| number: #0.##%]` | -| Format a number as a currency | `currency` | | `[#field \| currency]` | -| Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | -| HTML encode a string | `html` | | `[#field \| html]` | +| Filter | Function | Arguments | Example | +| ------------------------------------------------ | ----------------------- | -------------------- | ---------------------------------------------------- | +| Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | +| Convert string to lower case | `lower` | | `[#field \| lower]` | +| Convert string to upper case | `upper` | | `[#field \| upper]` | +| Get content name from content picker value | `contentName` | | `[#field \| contentName]` | +| Get content property from content picker value | `contentPropertyValue` | | `[#field \| contentPropertyValue propertyAlias]` | +| Format a number | `number` | format string | `[#field \| number: #0.##%]` | +| Format a number as a currency | `currency` | | `[#field \| currency]` | +| Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | +| HTML encode a string | `html` | | `[#field \| html]` | +| Truncate a string | `truncate` | number of characters | `[#field \| truncate: 10]` | + The format strings used for formatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. diff --git a/14/umbraco-forms/developer/magic-strings.md b/14/umbraco-forms/developer/magic-strings.md index 4ab8372d881..59249d546c6 100644 --- a/14/umbraco-forms/developer/magic-strings.md +++ b/14/umbraco-forms/developer/magic-strings.md @@ -82,16 +82,18 @@ For example, to truncate a string value read from an Umbraco page field with ali Umbraco Forms ships with the following filters: -| Filter | Function | Arguments | Example | -| ----------------------------- | ---------- | -------------------- | ------------------------------------ | -| Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | -| Convert string to lower case | `lower` | | `[#field \| lower]` | -| Convert string to upper case | `upper` | | `[#field \| upper]` | -| Truncate a string | `truncate` | number of characters | `[#field \| truncate: 10]` | -| Format a number | `number` | format string | `[#field \| number: #0.##%]` | -| Format a number as a currency | `currency` | | `[#field \| currency]` | -| Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | -| HTML encode a string | `html` | | `[#field \| html]` | +| Filter | Function | Arguments | Example | +| ------------------------------------------------ | ----------------------- | -------------------- | ---------------------------------------------------- | +| Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | +| Convert string to lower case | `lower` | | `[#field \| lower]` | +| Convert string to upper case | `upper` | | `[#field \| upper]` | +| Get content name from content picker value | `contentName` | | `[#field \| contentName]` | +| Get content property from content picker value | `contentPropertyValue` | | `[#field \| contentPropertyValue propertyAlias]` | +| Format a number | `number` | format string | `[#field \| number: #0.##%]` | +| Format a number as a currency | `currency` | | `[#field \| currency]` | +| Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | +| HTML encode a string | `html` | | `[#field \| html]` | +| Truncate a string | `truncate` | number of characters | `[#field \| truncate: 10]` | The format strings used for formatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. From 44840e1ff62abfdc2723aeaffbcaae05000307aa Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Fri, 21 Jun 2024 07:49:21 +0200 Subject: [PATCH 05/38] Added details of SupportsHtml setting attribute. --- 10/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 +- 12/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 +- 13/umbraco-forms/developer/extending/adding-a-fieldtype.md | 4 +++- 14/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 ++ 4 files changed, 7 insertions(+), 3 deletions(-) diff --git a/10/umbraco-forms/developer/extending/adding-a-fieldtype.md b/10/umbraco-forms/developer/extending/adding-a-fieldtype.md index a16af90542d..553ca10705d 100644 --- a/10/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/10/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -166,7 +166,7 @@ To reference the file the setting should be configured with a full path to the v [Setting("My Setting", Description = "Help text for the setting", View = "~/App_Plugins/UmbracoFormsCustomFields/backoffice/Common/SettingTypes/mycustomsettingfield.html", - SupportsPlaceholders = "true" + SupportsPlaceholders = true DisplayOrder = 10)] public string MySetting { get; set; } ``` diff --git a/12/umbraco-forms/developer/extending/adding-a-fieldtype.md b/12/umbraco-forms/developer/extending/adding-a-fieldtype.md index 424abd7abb1..655fa56e2e3 100644 --- a/12/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/12/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -165,7 +165,7 @@ To reference the file the setting should be configured with a full path to the v [Setting("My Setting", Description = "Help text for the setting", View = "~/App_Plugins/UmbracoFormsCustomFields/backoffice/Common/SettingTypes/mycustomsettingfield.html", - SupportsPlaceholders = "true" + SupportsPlaceholders = true DisplayOrder = 10)] public virtual string MySetting { get; set; } ``` diff --git a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md index 424abd7abb1..793e40e7c4a 100644 --- a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -165,7 +165,7 @@ To reference the file the setting should be configured with a full path to the v [Setting("My Setting", Description = "Help text for the setting", View = "~/App_Plugins/UmbracoFormsCustomFields/backoffice/Common/SettingTypes/mycustomsettingfield.html", - SupportsPlaceholders = "true" + SupportsPlaceholders = true, DisplayOrder = 10)] public virtual string MySetting { get; set; } ``` @@ -174,6 +174,8 @@ public virtual string MySetting { get; set; } `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). +`SupportsHtml` is a flag indicating whether the setting can contain HTML content and will be treated as such when the value is read from the Forms delivery API. + `IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. ### Settings when inheriting diff --git a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md index 27d0311a728..6f9c5dea91b 100644 --- a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -142,6 +142,8 @@ The `View` property indicates a property editor UI used for editing the setting `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). +`SupportsHtml` is a flag indicating whether the setting can contain HTML content and will be treated as such when the value is read from the Forms delivery API. + `IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. When creating a field or other provider type, you might choose to inherit from an existing class. This could be if one of the types provided with Umbraco Forms almost meets your needs but you want to make some changes. From ca92d1cba1b78970466580b9bb2c167d9ea60973 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Fri, 21 Jun 2024 16:35:04 +0200 Subject: [PATCH 06/38] Added details and release notes on the provision of additional data when rendering and submitting forms. --- .../assets/umbraco_forms_swagger.json | 48 ++++++++++++++----- 13/umbraco-forms/developer/ajaxforms.md | 12 ++++- 13/umbraco-forms/developer/magic-strings.md | 6 +++ 13/umbraco-forms/developer/rendering-forms.md | 9 ++-- 13/umbraco-forms/release-notes.md | 1 + .../assets/umbraco_forms_swagger.json | 18 +++++++ 14/umbraco-forms/developer/ajaxforms.md | 6 ++- 14/umbraco-forms/developer/magic-strings.md | 6 +++ 14/umbraco-forms/developer/rendering-forms.md | 9 ++-- 14/umbraco-forms/release-notes.md | 1 + 10 files changed, 95 insertions(+), 21 deletions(-) diff --git a/13/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json b/13/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json index 72ab43653f3..2e77da8be31 100644 --- a/13/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json +++ b/13/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json @@ -37,11 +37,22 @@ "schema": { "type": "string" } + }, + { + "name": "additionalData", + "in": "query", + "description": "Additional data provided when rendering the form.", + "schema": { + "type": "object", + "additionalProperties": { + "type": "string" + } + } } ], "responses": { "200": { - "description": "Success", + "description": "OK", "content": { "application/json": { "schema": { @@ -124,7 +135,7 @@ } }, "422": { - "description": "Client Error", + "description": "Unprocessable Content", "content": { "application/json": { "schema": { @@ -144,16 +155,14 @@ "Show", "Hide" ], - "type": "integer", - "format": "int32" + "type": "string" }, "FieldConditionLogicType": { "enum": [ "All", "Any" ], - "type": "integer", - "format": "int32" + "type": "string" }, "FieldConditionRuleOperator": { "enum": [ @@ -162,11 +171,19 @@ "GreaterThen", "LessThen", "Contains", + "ContainsIgnoreCase", "StartsWith", - "EndsWith" + "StartsWithIgnoreCase", + "EndsWith", + "EndsWithIgnoreCase", + "NotContains", + "NotContainsIgnoreCase", + "NotStartsWith", + "NotStartsWithIgnoreCase", + "NotEndsWith", + "NotEndsWithIgnoreCase" ], - "type": "integer", - "format": "int32" + "type": "string" }, "FormConditionDto": { "type": "object", @@ -285,6 +302,13 @@ "culture": { "type": "string", "nullable": true + }, + "additionalData": { + "type": "object", + "additionalProperties": { + "type": "string" + }, + "nullable": true } }, "additionalProperties": false @@ -305,7 +329,8 @@ }, "placeholder": { "type": "string", - "nullable": true + "nullable": true, + "deprecated": true }, "cssClass": { "type": "string", @@ -359,8 +384,7 @@ "MarkMandatoryFields", "MarkOptionalFields" ], - "type": "integer", - "format": "int32" + "type": "string" }, "FormFieldPrevalueDto": { "type": "object", diff --git a/13/umbraco-forms/developer/ajaxforms.md b/13/umbraco-forms/developer/ajaxforms.md index cfaae9dde4b..02c710104b0 100644 --- a/13/umbraco-forms/developer/ajaxforms.md +++ b/13/umbraco-forms/developer/ajaxforms.md @@ -43,7 +43,7 @@ The Open API specification is available from: `/umbraco/swagger/forms/swagger.js To request the definition of a form, the following request can be made: ```none -GET /umbraco/forms/api/v1/definitions/{id}?contentId={contentId}&culture={culture} +GET /umbraco/forms/api/v1/definitions/{id}?contentId={contentId}&culture={culture}&additionalData[{key}]={value}&additionalData[key2]={value2} ``` The GET request requires the Guid identifying the form. @@ -52,6 +52,8 @@ An optional `contentId` parameter can be provided, which can either be the integ A `culture` parameter can also be provided, expected as an ISO code identifying a language used in the Umbraco installation (for example, `en-US`). This will be used to ensure the correct translation for dictionary keys is used. It will also retrieve page content from the appropriate language variant. If the parameter is not provided in the request, the default Umbraco language will be used. +Finally an `additionalData` parameter can be provided in the form of a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). + If the requested form is not found, a 404 status code will be returned. A successful request will return a 200 status code. An example response is as follows. It will differ depending on the pages, fields and other settings available for the form. @@ -398,7 +400,11 @@ It also requires a `Content-Type` header of `application/json` and accepts a bod "dataConsent": "on" }, "contentId": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "culture": "en-US" + "culture": "en-US", + "additionalData": { + "foo": "bar", + "bax": "buzz", + } } ``` @@ -406,6 +412,8 @@ The `values` collection consists of a set of name/value pairs, where the name is The `contentId` and `culture` parameters are optional. If provided they will be used to customize the response for the current page and language respectively. +Similarly the `additionalData` dictionary is optional. This data is associated with the created record and made available within workflows. + In the case of a validation error, a 422 "Unprocessable Entity" status code will be returned, along with a response similar to the following: ```json diff --git a/13/umbraco-forms/developer/magic-strings.md b/13/umbraco-forms/developer/magic-strings.md index 7e9b174f5b6..d1323dd3ec5 100644 --- a/13/umbraco-forms/developer/magic-strings.md +++ b/13/umbraco-forms/developer/magic-strings.md @@ -50,6 +50,12 @@ Some extra variables are: `[$myRecursiveItem]` this allows you to parse the Umbraco Document Type property myRecursiveItem. So if the current page does not contain a value for this then it will request it from the parent up until the root or until it finds a value. +### Additional data + +When rendering a form, additional data can be provided in the form of a dictionary. As well as being associated with the created record and available within workflows, they can be used for "magic string" replacements. + +They are accessed using this syntax: `[+additionalDataKey]`. + ### Umbraco Form field `{myAliasForFormField}` this allows you to display the entered value for that specific field from the form submission. Used in workflows to send an automated email back to the customer based on the email address submitted in the form. The value here needs to be the alias of the field, and not the name of the field. diff --git a/13/umbraco-forms/developer/rendering-forms.md b/13/umbraco-forms/developer/rendering-forms.md index 552310534fd..dad5fee6c06 100644 --- a/13/umbraco-forms/developer/rendering-forms.md +++ b/13/umbraco-forms/developer/rendering-forms.md @@ -14,18 +14,20 @@ To display a form in your view, you can make a call to a view component: @await Component.InvokeAsync("RenderForm", new { formId = Guid.Parse("
"), theme = "default", includeScripts = false }) ``` -Five parameters can be provided: +Six parameters can be provided: - `formId` is the GUID of a form. - `theme` is the name of a theme. If not provided, the default theme is used (see [Themes](./themes.md)). - `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md). - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. +- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. Usually, rather than hard-coding the form's GUID and other details, you'll use a form, theme or content picker on your page: ```csharp -@await Component.InvokeAsync("RenderForm", new { formId = @Model.Form, theme = @Model.Theme, includeScripts = false }) +var additionalData = new Dictionary { { "foo", "bar" }, { "buzz", "baz" } }; +@await Component.InvokeAsync("RenderForm", new { formId = @Model.Form, theme = @Model.Theme, includeScripts = false, additionalData }) ``` ## Rendering Using a Tag Helper @@ -43,7 +45,8 @@ Then in your view you can use: ```csharp @if (Model.Form.HasValue) { - + var additionalData = new Dictionary { { "foo", "bar" }, { "buzz", "baz" } }; + } ``` diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 169536a2bfa..5599ee5183f 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -23,6 +23,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) * Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#868](https://github.com/umbraco/Umbraco.Forms.Issues/issues/868) * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230) * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). diff --git a/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json b/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json index f86212a522e..360a0c02bf4 100644 --- a/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json +++ b/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json @@ -37,6 +37,17 @@ "schema": { "type": "string" } + }, + { + "name": "additionalData", + "in": "query", + "description": "Additional data provided when rendering the form.", + "schema": { + "type": "object", + "additionalProperties": { + "type": "string" + } + } } ], "responses": { @@ -285,6 +296,13 @@ "culture": { "type": "string", "nullable": true + }, + "additionalData": { + "type": "object", + "additionalProperties": { + "type": "string" + }, + "nullable": true } }, "additionalProperties": false diff --git a/14/umbraco-forms/developer/ajaxforms.md b/14/umbraco-forms/developer/ajaxforms.md index 83a008b0e95..683a44d6a70 100644 --- a/14/umbraco-forms/developer/ajaxforms.md +++ b/14/umbraco-forms/developer/ajaxforms.md @@ -43,7 +43,7 @@ The Open API specification is available from: `/umbraco/swagger/forms/swagger.js To request the definition of a form, the following request can be made: ```none -GET /umbraco/forms/delivery/api/v1/definitions/{id}?contentId={contentId}&culture={culture} +GET /umbraco/forms/delivery/api/v1/definitions/{id}?contentId={contentId}&culture={culture}&additionalData[{key}]={value}&additionalData[key2]={value2} ``` The GET request requires the Guid identifying the form. @@ -52,6 +52,8 @@ An optional `contentId` parameter can be provided, which can either be the integ A `culture` parameter can also be provided, expected as an ISO code identifying a language used in the Umbraco installation (for example, `en-US`). This will be used to ensure the correct translation for dictionary keys is used. It will also retrieve page content from the appropriate language variant. If the parameter is not provided in the request, the default Umbraco language will be used. +Finally an `additionalData` parameter can be provided in the form of a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). + If the requested form is not found, a 404 status code will be returned. A successful request will return a 200 status code. An example response is as follows. It will differ depending on the pages, fields and other settings available for the form. @@ -406,6 +408,8 @@ The `values` collection consists of a set of name/value pairs, where the name is The `contentId` and `culture` parameters are optional. If provided they will be used to customize the response for the current page and language respectively. +Similarly the `additionalData` dictionary is optional. This data is associated with the created record and made available within workflows. + In the case of a validation error, a 422 "Unprocessable Entity" status code will be returned, along with a response similar to the following: ```json diff --git a/14/umbraco-forms/developer/magic-strings.md b/14/umbraco-forms/developer/magic-strings.md index 59249d546c6..ede1a1c8436 100644 --- a/14/umbraco-forms/developer/magic-strings.md +++ b/14/umbraco-forms/developer/magic-strings.md @@ -50,6 +50,12 @@ Some extra variables are: `[$myRecursiveItem]` this allows you to parse the Umbraco Document Type property myRecursiveItem. So if the current page does not contain a value for this then it will request it from the parent up until the root or until it finds a value. +### Additional data + +When rendering a form, additional data can be provided in the form of a dictionary. As well as being associated with the created record and available within workflows, they can be used for "magic string" replacements. + +They are accessed using this syntax: `[+additionalDataKey]`. + ### Umbraco Form field `{myAliasForFormField}` this allows you to display the entered value for that specific field from the form submission. Used in workflows to send an automated email back to the customer based on the email address submitted in the form. The value here needs to be the alias of the field, and not the name of the field. diff --git a/14/umbraco-forms/developer/rendering-forms.md b/14/umbraco-forms/developer/rendering-forms.md index 552310534fd..dad5fee6c06 100644 --- a/14/umbraco-forms/developer/rendering-forms.md +++ b/14/umbraco-forms/developer/rendering-forms.md @@ -14,18 +14,20 @@ To display a form in your view, you can make a call to a view component: @await Component.InvokeAsync("RenderForm", new { formId = Guid.Parse(""), theme = "default", includeScripts = false }) ``` -Five parameters can be provided: +Six parameters can be provided: - `formId` is the GUID of a form. - `theme` is the name of a theme. If not provided, the default theme is used (see [Themes](./themes.md)). - `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md). - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. +- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. Usually, rather than hard-coding the form's GUID and other details, you'll use a form, theme or content picker on your page: ```csharp -@await Component.InvokeAsync("RenderForm", new { formId = @Model.Form, theme = @Model.Theme, includeScripts = false }) +var additionalData = new Dictionary { { "foo", "bar" }, { "buzz", "baz" } }; +@await Component.InvokeAsync("RenderForm", new { formId = @Model.Form, theme = @Model.Theme, includeScripts = false, additionalData }) ``` ## Rendering Using a Tag Helper @@ -43,7 +45,8 @@ Then in your view you can use: ```csharp @if (Model.Form.HasValue) { - + var additionalData = new Dictionary { { "foo", "bar" }, { "buzz", "baz" } }; + } ``` diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index 4cde0105f1a..b6ddda9411f 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -23,6 +23,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) * Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#868](https://github.com/umbraco/Umbraco.Forms.Issues/issues/868) * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) From 4538ced910f6504fe33ca321cc74be042770f0cf Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Fri, 21 Jun 2024 17:48:25 +0200 Subject: [PATCH 07/38] Fixed issue link. --- 13/umbraco-forms/release-notes.md | 2 +- 14/umbraco-forms/release-notes.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 5599ee5183f..e965ccf7400 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -23,7 +23,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) * Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) -* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#868](https://github.com/umbraco/Umbraco.Forms.Issues/issues/868) +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230) * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index b6ddda9411f..78d7faa8dd6 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -23,7 +23,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) * Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) -* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#868](https://github.com/umbraco/Umbraco.Forms.Issues/issues/868) +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) From 84e72b864b9d62f30b751d9c6b4dab44d6a0fce7 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 1 Jul 2024 06:53:25 +0200 Subject: [PATCH 08/38] Added additional item in release notes. --- 13/umbraco-forms/developer/ajaxforms.md | 2 +- 13/umbraco-forms/release-notes.md | 25 +++++++++++++------------ 14/umbraco-forms/developer/ajaxforms.md | 8 ++++++-- 14/umbraco-forms/release-notes.md | 1 + 4 files changed, 21 insertions(+), 15 deletions(-) diff --git a/13/umbraco-forms/developer/ajaxforms.md b/13/umbraco-forms/developer/ajaxforms.md index 02c710104b0..49c7e9bc820 100644 --- a/13/umbraco-forms/developer/ajaxforms.md +++ b/13/umbraco-forms/developer/ajaxforms.md @@ -403,7 +403,7 @@ It also requires a `Content-Type` header of `application/json` and accepts a bod "culture": "en-US", "additionalData": { "foo": "bar", - "bax": "buzz", + "baz": "buzz", } } ``` diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index e965ccf7400..b940638a53c 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -19,23 +19,24 @@ This section contains the release notes for Umbraco Forms 13 including all chang #### [**13.2.0**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(TBC)** -* Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) +* Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) -* Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) -* Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) -* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) -* Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) -* Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230) +* Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210). +* Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205). +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578). +* Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183). +* Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230). * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). * Resolved duplicate approval occurring when record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). -* Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220) -* Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219) -* Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214) -* Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206) +* Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220). +* Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). +* Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). +* Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206). * Added setting option for the "send to URL" workflow to switch between caption and alias for the field value's XML element [#1202](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1202) -* Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) +* Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221). * Restored target used to generate local configuration schema information [#1226](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1226). -* Fixed issues with retrieving fields and assigning default values when using the datasource wizard +* Fixed issues with retrieving fields and assigning default values when using the datasource wizard. +* Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** diff --git a/14/umbraco-forms/developer/ajaxforms.md b/14/umbraco-forms/developer/ajaxforms.md index 683a44d6a70..e2c27558f1a 100644 --- a/14/umbraco-forms/developer/ajaxforms.md +++ b/14/umbraco-forms/developer/ajaxforms.md @@ -21,7 +21,7 @@ For example: ## API Definition The API supports two endpoints, one for rendering a form and one for submitting it. - +entri {% swagger src="../.gitbook/assets/umbraco_forms_swagger.json" path="/umbraco/forms/delivery/api/v1/definitions/{id}" method="get" %} [umbraco_forms_swagger.json](../.gitbook/assets/umbraco_forms_swagger.json) {% endswagger %} @@ -400,7 +400,11 @@ It also requires a `Content-Type` header of `application/json` and accepts a bod "dataConsent": "on" }, "contentId": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "culture": "en-US" + "culture": "en-US", + "additionalData": { + "foo": "bar", + "baz": "buzz", + } } ``` diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index 78d7faa8dd6..bf7ce25352d 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -26,6 +26,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) +* Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). #### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** From 60887a07e268376b029ac5a29fb852aedf8d6afe Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 1 Jul 2024 07:26:12 +0200 Subject: [PATCH 09/38] Updated release notes. --- 13/umbraco-forms/release-notes.md | 1 + 14/umbraco-forms/release-notes.md | 1 + 2 files changed, 2 insertions(+) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index b940638a53c..76e47ffbb16 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -37,6 +37,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Restored target used to generate local configuration schema information [#1226](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1226). * Fixed issues with retrieving fields and assigning default values when using the datasource wizard. * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). +* Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index bf7ce25352d..c5043acc037 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -27,6 +27,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). +* Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). #### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** From 024a2f117659e09e4bc0a8a2ad0c25d3a892d386 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 07:34:58 +0200 Subject: [PATCH 10/38] Tidy up. --- 13/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 -- 13/umbraco-forms/developer/rendering-forms.md | 2 +- 14/umbraco-forms/developer/ajaxforms.md | 2 +- 14/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 -- 14/umbraco-forms/developer/rendering-forms.md | 2 +- 5 files changed, 3 insertions(+), 7 deletions(-) diff --git a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md index 765d25a3ff3..793e40e7c4a 100644 --- a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -172,8 +172,6 @@ public virtual string MySetting { get; set; } `SupportsPlaceholders` is a flag indicating whether the setting can contain ["magic string" placeholders](../magic-strings.md) and controls whether they are parsed on rendering. -`SupportsHtml` is a flag indicating whether the setting contains HTML markup. - `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). `SupportsHtml` is a flag indicating whether the setting can contain HTML content and will be treated as such when the value is read from the Forms delivery API. diff --git a/13/umbraco-forms/developer/rendering-forms.md b/13/umbraco-forms/developer/rendering-forms.md index dad5fee6c06..77f17bb3060 100644 --- a/13/umbraco-forms/developer/rendering-forms.md +++ b/13/umbraco-forms/developer/rendering-forms.md @@ -21,7 +21,7 @@ Six parameters can be provided: - `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md). - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. -- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. +- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic or update within workflows. Usually, rather than hard-coding the form's GUID and other details, you'll use a form, theme or content picker on your page: diff --git a/14/umbraco-forms/developer/ajaxforms.md b/14/umbraco-forms/developer/ajaxforms.md index e2c27558f1a..54b629b4b30 100644 --- a/14/umbraco-forms/developer/ajaxforms.md +++ b/14/umbraco-forms/developer/ajaxforms.md @@ -21,7 +21,7 @@ For example: ## API Definition The API supports two endpoints, one for rendering a form and one for submitting it. -entri + {% swagger src="../.gitbook/assets/umbraco_forms_swagger.json" path="/umbraco/forms/delivery/api/v1/definitions/{id}" method="get" %} [umbraco_forms_swagger.json](../.gitbook/assets/umbraco_forms_swagger.json) {% endswagger %} diff --git a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md index f9ed2283037..6f9c5dea91b 100644 --- a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -140,8 +140,6 @@ The `View` property indicates a property editor UI used for editing the setting `SupportsPlaceholders` is a flag indicating whether the setting can contain ["magic string" placeholders](../magic-strings.md) and controls whether they are parsed on rendering. -`SupportsHtml` is a flag indicating whether the setting contains HTML markup. - `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). `SupportsHtml` is a flag indicating whether the setting can contain HTML content and will be treated as such when the value is read from the Forms delivery API. diff --git a/14/umbraco-forms/developer/rendering-forms.md b/14/umbraco-forms/developer/rendering-forms.md index dad5fee6c06..77f17bb3060 100644 --- a/14/umbraco-forms/developer/rendering-forms.md +++ b/14/umbraco-forms/developer/rendering-forms.md @@ -21,7 +21,7 @@ Six parameters can be provided: - `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md). - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. -- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. +- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic or update within workflows. Usually, rather than hard-coding the form's GUID and other details, you'll use a form, theme or content picker on your page: From 45944c7993a9725f70c34bfaf894a788aed4d82f Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 07:38:46 +0200 Subject: [PATCH 11/38] Linting. --- 13/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 +- 14/umbraco-forms/developer/extending/adding-a-fieldtype.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md index 793e40e7c4a..7821eecf05c 100644 --- a/13/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/13/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -174,7 +174,7 @@ public virtual string MySetting { get; set; } `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). -`SupportsHtml` is a flag indicating whether the setting can contain HTML content and will be treated as such when the value is read from the Forms delivery API. +`SupportsHtml` is a flag indicating whether the setting can contain HTML content. When set to `true` it will be treated as HTML content when the value is read from the Forms delivery API. `IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. diff --git a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md index 6f9c5dea91b..67f93506c49 100644 --- a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md @@ -142,7 +142,7 @@ The `View` property indicates a property editor UI used for editing the setting `HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). -`SupportsHtml` is a flag indicating whether the setting can contain HTML content and will be treated as such when the value is read from the Forms delivery API. +`SupportsHtml` is a flag indicating whether the setting can contain HTML content. When set to `true` it will be treated as HTML content when the value is read from the Forms delivery API. `IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. From 6be5d3dbab08097ae4f5a2a35862bb012fb37bb1 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 07:55:30 +0200 Subject: [PATCH 12/38] Removed reference to reverted feature. --- 13/umbraco-forms/developer/magic-strings.md | 2 -- 13/umbraco-forms/release-notes.md | 3 +-- 14/umbraco-forms/developer/magic-strings.md | 2 -- 14/umbraco-forms/release-notes.md | 3 +-- 4 files changed, 2 insertions(+), 8 deletions(-) diff --git a/13/umbraco-forms/developer/magic-strings.md b/13/umbraco-forms/developer/magic-strings.md index d1323dd3ec5..04f5128c2ee 100644 --- a/13/umbraco-forms/developer/magic-strings.md +++ b/13/umbraco-forms/developer/magic-strings.md @@ -93,8 +93,6 @@ Umbraco Forms ships with the following filters: | Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | | Convert string to lower case | `lower` | | `[#field \| lower]` | | Convert string to upper case | `upper` | | `[#field \| upper]` | -| Get content name from content picker value | `contentName` | | `[#field \| contentName]` | -| Get content property from content picker value | `contentPropertyValue` | | `[#field \| contentPropertyValue propertyAlias]` | | Format a number | `number` | format string | `[#field \| number: #0.##%]` | | Format a number as a currency | `currency` | | `[#field \| currency]` | | Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 76e47ffbb16..48b682210dd 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -22,8 +22,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210). -* Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205). -* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578). +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic and update within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578). * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183). * Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230). * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). diff --git a/14/umbraco-forms/developer/magic-strings.md b/14/umbraco-forms/developer/magic-strings.md index ede1a1c8436..984580e8125 100644 --- a/14/umbraco-forms/developer/magic-strings.md +++ b/14/umbraco-forms/developer/magic-strings.md @@ -93,8 +93,6 @@ Umbraco Forms ships with the following filters: | Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | | Convert string to lower case | `lower` | | `[#field \| lower]` | | Convert string to upper case | `upper` | | `[#field \| upper]` | -| Get content name from content picker value | `contentName` | | `[#field \| contentName]` | -| Get content property from content picker value | `contentPropertyValue` | | `[#field \| contentPropertyValue propertyAlias]` | | Format a number | `number` | format string | `[#field \| number: #0.##%]` | | Format a number as a currency | `currency` | | `[#field \| currency]` | | Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index c5043acc037..44cf4b35e3f 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -22,8 +22,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) -* Added placeholder format functions to resolve content name and property values from content picker [#1205](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1205) -* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) +* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic and update within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). From 47e868c315b0b8143ea16db80545f46a7201002e Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 08:14:15 +0200 Subject: [PATCH 13/38] Updated release notes. --- 13/umbraco-forms/release-notes.md | 1 + 14/umbraco-forms/release-notes.md | 1 + 2 files changed, 2 insertions(+) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 48b682210dd..3a0ae55ac53 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -37,6 +37,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Fixed issues with retrieving fields and assigning default values when using the datasource wizard. * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). +* Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index 44cf4b35e3f..e9ab19c9e52 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -27,6 +27,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). +* Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). #### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** From e8a4c1bb994854ef2bf48666b9877d50be4b342d Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 08:47:54 +0200 Subject: [PATCH 14/38] Further release notes. --- 13/umbraco-forms/release-notes.md | 1 + 14/umbraco-forms/release-notes.md | 1 + 2 files changed, 2 insertions(+) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 3a0ae55ac53..ab29398c64e 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -38,6 +38,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). +* Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index e9ab19c9e52..fda9176bd0a 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -28,6 +28,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). +* Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). #### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** From 55c32aff2cb22eec338d19730e3897b37b8392b3 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 10:40:12 +0200 Subject: [PATCH 15/38] Updated release notes. --- 14/umbraco-forms/release-notes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index fda9176bd0a..e8da97651f2 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -29,6 +29,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). * Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). +* Resolved issues with intermittent failures of the form entries table display [#1239](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1239). #### [**14.0.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(June 11th 2024)** From 6ccf473fa80a045671c48f2662f4c4b6f7cdb7dc Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 10:50:30 +0200 Subject: [PATCH 16/38] Updated type details. --- 13/umbraco-forms/developer/configuration/type-details.md | 2 ++ 14/umbraco-forms/developer/configuration/type-details.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/13/umbraco-forms/developer/configuration/type-details.md b/13/umbraco-forms/developer/configuration/type-details.md index 0ad7a1f35bc..723648393c3 100644 --- a/13/umbraco-forms/developer/configuration/type-details.md +++ b/13/umbraco-forms/developer/configuration/type-details.md @@ -130,6 +130,7 @@ The intention is to be able to make available details such as IDs, aliases and p **Settings:** +* `DisplayLayout` * `DefaultValue` * `ShowLabel` @@ -206,6 +207,7 @@ The intention is to be able to make available details such as IDs, aliases and p **Settings:** +* `DisplayLayout` * `DefaultValue` * `ShowLabel` diff --git a/14/umbraco-forms/developer/configuration/type-details.md b/14/umbraco-forms/developer/configuration/type-details.md index 0ad7a1f35bc..723648393c3 100644 --- a/14/umbraco-forms/developer/configuration/type-details.md +++ b/14/umbraco-forms/developer/configuration/type-details.md @@ -130,6 +130,7 @@ The intention is to be able to make available details such as IDs, aliases and p **Settings:** +* `DisplayLayout` * `DefaultValue` * `ShowLabel` @@ -206,6 +207,7 @@ The intention is to be able to make available details such as IDs, aliases and p **Settings:** +* `DisplayLayout` * `DefaultValue` * `ShowLabel` From 0426a69a77ee87cd36bd9b4ce3bdcb8110612e34 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 11:49:06 +0200 Subject: [PATCH 17/38] Added setting type details. --- .../developer/extending/setting-types.md | 51 ++++++++++--------- 1 file changed, 28 insertions(+), 23 deletions(-) diff --git a/14/umbraco-forms/developer/extending/setting-types.md b/14/umbraco-forms/developer/extending/setting-types.md index 41504f56c12..11eb05e5bdb 100644 --- a/14/umbraco-forms/developer/extending/setting-types.md +++ b/14/umbraco-forms/developer/extending/setting-types.md @@ -6,42 +6,47 @@ These settings are completed by the editor when using the type on their form. Each setting type can have it's own user interface. So a string can use a text box but a more complicated JSON structure can use a more appropriate user interface. +From Forms 14, each interface is defined as an Umbraco [property editor UI](https://docs.umbraco.com/umbraco-cms/extending/property-editors/composition/property-editor-ui). + The user interface used for a particular setting is defined by the `View` property: ```csharp -[Umbraco.Forms.Core.Attributes.Setting("Message", View = "TextField")] +[Umbraco.Forms.Core.Attributes.Setting("Message", View = "Umb.PropertyEditorUi.TextBox")] public string Message { get; set; } ``` +If not specified, the default `Umb.PropertyEditorUi.TextBox` is used. + ## Built-in setting types The following setting types are available and are used for the field, prevalue source and workflow types that ship with the package. -| Name | Description | Used in | -|---------------------------|-------------------------------------------------------------------|-------------------------------------------------| -| Checkbox | Uses a single checkbox for entry | | -| DocumentMapper | Used for selection of a documenttype | The "Save as Umbraco node" workflow | -| Dropdownlist | Used for selection from a list of options | | -| EmailTemplatePicker | Used for selection of an email template | The "Send email with Razor template" workflow | -| FieldMapper | Used to map fields from a form to required aliases | The "Send to URL" workflow | -| File | Used for selection of a file | The "Send email with XSLT template" workflow | -| NumericField | Uses numerical text box for entry | | -| Password | Uses password text box for entry | | -| PasswordNoAutocomplete | Uses password text box for entry (with autocomplete disabled) | | -| Pickers.ContentWithXPath | Uses a content picker with the option for XPath entry | The "Save as Umbraco node" workflow | -| Pickers.Datatype | Uses a datatype picker | The "Umbraco prevalues" prevalue source | -| Pickers.DocumentType | Uses a document picker | The "Umbraco nodes" prevalue source | -| Range | Uses a slider for range input | The "reCAPTCHAv3" field type | -| RichText | Uses a rich text editor for input | The "Send email" workflows | -| StandardFieldMapper | Used to map system fields from a form to required aliases | The "Send to URL" workflow | -| Textarea | Used a multiline textbox for entry | | -| Textfield | Used a single-line textbox for entry | | -| TextfieldNoAutocomplete | Used a single-line textbox for entry (with autocomplete disabled) | | -| TextWithFieldPicker | Used a single-line textbox/form field list for entry | Not used in core types | +Some are defined with the Umbraco CMS and some ship with the Forms package. + +| Name | Source | Description | Used in | +|--------------------------------------------------|--------------|-------------------------------------------------------------------|-------------------------------------------------| +| Umb.PropertyEditorUi.ContentPicker.Source | CMS | Uses a content picker with the option for XPath entry | The "Save as Umbraco node" workflow | +| Umb.PropertyEditorUi.Dropdown | CMS | Used for selection from a list of options | | +| Umb.PropertyEditorUi.Integer | CMS | Uses numerical text box for entry | | +| Umb.PropertyEditorUi.MultipleTextString | CMS | Uses multiple text boxes for entry | Not used in core types | +| Umb.PropertyEditorUi.Slider | CMS | Uses a slider for range input | The "reCAPTCHAv3" field type | +| Umb.PropertyEditorUi.TextArea | CMS | Used a multiline textbox for entry | | +| Umb.PropertyEditorUi.TextBox | CMS | Used a single-line textbox for entry | | +| Umb.PropertyEditorUi.TinyMCE | CMS | Uses a rich text editor for input | The "Send email" workflows | +| Umb.PropertyEditorUi.Toggle | CMS | Uses a single checkbox for entry | | +| Umb.PropertyEditorUi.UploadField | CMS | Used for selection of a file | The "Send email with XSLT template" workflow | +| Forms.PropertyEditorUi.DataTypePicker | Forms | Uses a datatype picker | The "Umbraco prevalues" prevalue source | +| Forms.PropertyEditorUi.DocumentTypePicker | Forms | Uses a document picker | The "Umbraco nodes" prevalue source | +| Forms.PropertyEditorUi.DocumentMapper | Forms | Used for selection of a documenttype | The "Save as Umbraco node" workflow | +| Forms.PropertyEditorUi.EmailTemplatePicker | Forms | Used for selection of an email template | The "Send email with Razor template" workflow | +| Forms.PropertyEditorUi.FieldMapper | Forms | Used to map fields from a form to required aliases | The "Send to URL" workflow | +| Forms.PropertyEditorUi.Password | Forms | Uses password text box for entry | | +| Forms.PropertyEditorUi.StandardFieldMapper | Forms | Used to map system fields from a form to required aliases | The "Send to URL" workflow | +| Forms.PropertyEditorUi.TextWithFieldPicker | Forms | Used a single-line textbox/form field list for entry | Not used in core types | All of the above setting types are used in one or more field, prevalue source and workflow types available with Umbraco Forms. For the less common ones, a usage has been indicated in the table. -The one exception is the "TextWithFieldPicker". This one we don't use within the package, but we make it available for developers to use when creating their own types. +The one exception is `Forms.PropertyEditorUi.TextWithFieldPicker`. This one we don't use within the package, but we make it available for developers to use when creating their own types. It offers the option of text field entry or the selection of a field from the form. This can be useful in workflows where you need to reference the value of a specific field. From 73596a52a546ca1e750e4280b7b90a7351c1ce9b Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 2 Jul 2024 12:05:59 +0200 Subject: [PATCH 18/38] Added patch release notes and updated minors to first be released as RCs. --- 10/umbraco-forms/release-notes.md | 7 +++++++ 13/umbraco-forms/release-notes.md | 2 +- 14/umbraco-forms/release-notes.md | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/10/umbraco-forms/release-notes.md b/10/umbraco-forms/release-notes.md index 4419c43acbb..6f47f0b225e 100644 --- a/10/umbraco-forms/release-notes.md +++ b/10/umbraco-forms/release-notes.md @@ -21,6 +21,13 @@ This section contains the release notes for Umbraco Forms 8 and 10 including all Version 10 +[**10.5.6**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.5.6) **(TBC)** + +* Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). +* Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). +* Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206). +* Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). + [**10.5.5**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.5.5) **(April 16th 2024)** * Corrected alignment of label `for` and input `id` attributes in the date picker field [#1200](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1200). diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index ab29398c64e..5b6a0478f1e 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -17,7 +17,7 @@ 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.2.0**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(TBC)** +#### [**13.2.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(TBC)** * Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index e8da97651f2..bbc411929b9 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -17,7 +17,7 @@ If you are upgrading to a new major version, you can find information about the This section contains the release notes for Umbraco Forms 14 including all changes for this version. -#### [**14.1.0**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) **(TBC)** +#### [**14.1.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) **(TBC)** * Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) From b602596bb35d1bf4e55398f2d62b7adc9e031f50 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 8 Jul 2024 12:01:21 +0200 Subject: [PATCH 19/38] Updated release notes. --- 10/umbraco-forms/release-notes.md | 2 +- 13/umbraco-forms/release-notes.md | 3 ++- 14/umbraco-forms/release-notes.md | 2 +- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/10/umbraco-forms/release-notes.md b/10/umbraco-forms/release-notes.md index 6f47f0b225e..11a68008cb2 100644 --- a/10/umbraco-forms/release-notes.md +++ b/10/umbraco-forms/release-notes.md @@ -21,7 +21,7 @@ This section contains the release notes for Umbraco Forms 8 and 10 including all Version 10 -[**10.5.6**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.5.6) **(TBC)** +[**10.5.6**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.5.6) **(July 9th 2024)** * Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). * Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 5b6a0478f1e..9bf16aa2b94 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -17,7 +17,7 @@ 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.2.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(TBC)** +#### [**13.2.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(July 9th 2024)** * Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) @@ -39,6 +39,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). * Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). +* Improved support for editing large, multi-page forms by retaining scroll position between views and adding a "jump to page" option [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1243). #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index bbc411929b9..7a93c3839ee 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -17,7 +17,7 @@ If you are upgrading to a new major version, you can find information about the This section contains the release notes for Umbraco Forms 14 including all changes for this version. -#### [**14.1.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) **(TBC)** +#### [**14.1.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) **(July 9th 2024)** * Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) From 516f7e07398626088445ae0e95dbb93ef406af8c Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:37:37 +0200 Subject: [PATCH 20/38] Update 10/umbraco-forms/release-notes.md --- 10/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10/umbraco-forms/release-notes.md b/10/umbraco-forms/release-notes.md index 11a68008cb2..ed2d50d5885 100644 --- a/10/umbraco-forms/release-notes.md +++ b/10/umbraco-forms/release-notes.md @@ -23,7 +23,7 @@ This section contains the release notes for Umbraco Forms 8 and 10 including all [**10.5.6**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.5.6) **(July 9th 2024)** -* Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). +* Fixed issue with save button UI, when save is canceled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). * Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). * Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). From 1bb69fcfc94400725c861518b3b16cfdfe2daa7e Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:37:45 +0200 Subject: [PATCH 21/38] Update 10/umbraco-forms/release-notes.md --- 10/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10/umbraco-forms/release-notes.md b/10/umbraco-forms/release-notes.md index ed2d50d5885..d85522ed22c 100644 --- a/10/umbraco-forms/release-notes.md +++ b/10/umbraco-forms/release-notes.md @@ -24,7 +24,7 @@ This section contains the release notes for Umbraco Forms 8 and 10 including all [**10.5.6**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.5.6) **(July 9th 2024)** * Fixed issue with save button UI, when save is canceled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). -* Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). +* Improved date format for data values when using the **Send email** workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). * Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). From ee1e466ab2a96fcea8ea43f5845b341bce957933 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:37:52 +0200 Subject: [PATCH 22/38] Update 13/umbraco-forms/developer/ajaxforms.md --- 13/umbraco-forms/developer/ajaxforms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/developer/ajaxforms.md b/13/umbraco-forms/developer/ajaxforms.md index 49c7e9bc820..03177840570 100644 --- a/13/umbraco-forms/developer/ajaxforms.md +++ b/13/umbraco-forms/developer/ajaxforms.md @@ -52,7 +52,7 @@ An optional `contentId` parameter can be provided, which can either be the integ A `culture` parameter can also be provided, expected as an ISO code identifying a language used in the Umbraco installation (for example, `en-US`). This will be used to ensure the correct translation for dictionary keys is used. It will also retrieve page content from the appropriate language variant. If the parameter is not provided in the request, the default Umbraco language will be used. -Finally an `additionalData` parameter can be provided in the form of a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). +Finally, an `additionalData` parameter can be provided as a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). If the requested form is not found, a 404 status code will be returned. From 9efd453cc97a594e2a55e6fa47a3c921c9a35b3c Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:37:58 +0200 Subject: [PATCH 23/38] Update 13/umbraco-forms/developer/ajaxforms.md --- 13/umbraco-forms/developer/ajaxforms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/developer/ajaxforms.md b/13/umbraco-forms/developer/ajaxforms.md index 03177840570..560a7f3d41a 100644 --- a/13/umbraco-forms/developer/ajaxforms.md +++ b/13/umbraco-forms/developer/ajaxforms.md @@ -412,7 +412,7 @@ The `values` collection consists of a set of name/value pairs, where the name is The `contentId` and `culture` parameters are optional. If provided they will be used to customize the response for the current page and language respectively. -Similarly the `additionalData` dictionary is optional. This data is associated with the created record and made available within workflows. +Similarly, the `additionalData` dictionary is optional. This data is associated with the created record and made available within workflows. In the case of a validation error, a 422 "Unprocessable Entity" status code will be returned, along with a response similar to the following: From 28040f7e15b4ad53a4ae0ce989a24985396b900d Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:38:06 +0200 Subject: [PATCH 24/38] Update 13/umbraco-forms/developer/extending/setting-types.md --- 13/umbraco-forms/developer/extending/setting-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/developer/extending/setting-types.md b/13/umbraco-forms/developer/extending/setting-types.md index bb19b49d5ff..67bca9efa8b 100644 --- a/13/umbraco-forms/developer/extending/setting-types.md +++ b/13/umbraco-forms/developer/extending/setting-types.md @@ -25,7 +25,7 @@ The following setting types are available and are used for the field, prevalue s | EmailTemplatePicker | Used for selection of an email template | The "Send email with Razor template" workflow | | FieldMapper | Used to map fields from a form to required aliases | The "Send to URL" workflow | | File | Used for selection of a file | The "Send email with XSLT template" workflow | -| MultipleTextString | Used multiple textboxes for multiple entries | Not used in core types | +| MultipleTextString | Uses multiple text boxes for entry | Not used in core types | | NumericField | Uses numerical text box for entry | | | Password | Uses password text box for entry | | | PasswordNoAutocomplete | Uses password text box for entry (with autocomplete disabled) | | From 6c713bac8832e931dcfad5ce730947f273041656 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:38:13 +0200 Subject: [PATCH 25/38] Update 14/umbraco-forms/developer/extending/setting-types.md --- 14/umbraco-forms/developer/extending/setting-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/developer/extending/setting-types.md b/14/umbraco-forms/developer/extending/setting-types.md index 11eb05e5bdb..96359c4be59 100644 --- a/14/umbraco-forms/developer/extending/setting-types.md +++ b/14/umbraco-forms/developer/extending/setting-types.md @@ -31,7 +31,7 @@ Some are defined with the Umbraco CMS and some ship with the Forms package. | Umb.PropertyEditorUi.MultipleTextString | CMS | Uses multiple text boxes for entry | Not used in core types | | Umb.PropertyEditorUi.Slider | CMS | Uses a slider for range input | The "reCAPTCHAv3" field type | | Umb.PropertyEditorUi.TextArea | CMS | Used a multiline textbox for entry | | -| Umb.PropertyEditorUi.TextBox | CMS | Used a single-line textbox for entry | | +| Umb.PropertyEditorUi.TextBox | CMS | Uses a single-line textbox for entry | | | Umb.PropertyEditorUi.TinyMCE | CMS | Uses a rich text editor for input | The "Send email" workflows | | Umb.PropertyEditorUi.Toggle | CMS | Uses a single checkbox for entry | | | Umb.PropertyEditorUi.UploadField | CMS | Used for selection of a file | The "Send email with XSLT template" workflow | From 53b3482fec159bd79e4b2ea5be0304242e0dbb61 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:38:19 +0200 Subject: [PATCH 26/38] Update 14/umbraco-forms/developer/extending/setting-types.md --- 14/umbraco-forms/developer/extending/setting-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/developer/extending/setting-types.md b/14/umbraco-forms/developer/extending/setting-types.md index 96359c4be59..0cc4c3ee574 100644 --- a/14/umbraco-forms/developer/extending/setting-types.md +++ b/14/umbraco-forms/developer/extending/setting-types.md @@ -42,7 +42,7 @@ Some are defined with the Umbraco CMS and some ship with the Forms package. | Forms.PropertyEditorUi.FieldMapper | Forms | Used to map fields from a form to required aliases | The "Send to URL" workflow | | Forms.PropertyEditorUi.Password | Forms | Uses password text box for entry | | | Forms.PropertyEditorUi.StandardFieldMapper | Forms | Used to map system fields from a form to required aliases | The "Send to URL" workflow | -| Forms.PropertyEditorUi.TextWithFieldPicker | Forms | Used a single-line textbox/form field list for entry | Not used in core types | +| Forms.PropertyEditorUi.TextWithFieldPicker | Forms | Uses a single-line textbox/form field list for entry | Not used in core types | All of the above setting types are used in one or more field, prevalue source and workflow types available with Umbraco Forms. For the less common ones, a usage has been indicated in the table. From 1786a88255ba99516b5d3927c73d684f1dda9e4c Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:38:32 +0200 Subject: [PATCH 27/38] Update 14/umbraco-forms/release-notes.md --- 14/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index 7a93c3839ee..3bfec844b71 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -39,7 +39,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). * Restored target used to generate local configuration schema information [#1226](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1226). -* Resolved duplicate approval occurring when record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). +* Resolved duplicate approval occurring when the record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). * Added some missing localization keys and translations. * Fixed description of management API on Swagger UI. * Fixed display of specific form access list for user and group security. From a690d2dd43f24a56e111b97edf164004a11cdde2 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:38:55 +0200 Subject: [PATCH 28/38] Update 13/umbraco-forms/release-notes.md --- 13/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 9bf16aa2b94..f8687ff8307 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -26,7 +26,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183). * Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates [#1230](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1230). * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). -* Resolved duplicate approval occurring when record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). +* Resolved duplicate approval occurring when the record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). * Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220). * Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). * Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). From 31360914f456034b5f19bc5c40ec98da1b6dae6c Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:39:09 +0200 Subject: [PATCH 29/38] Update 13/umbraco-forms/release-notes.md --- 13/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index f8687ff8307..a266afcae3e 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -28,7 +28,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). * Resolved duplicate approval occurring when the record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). * Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220). -* Fixed issue with save button UI when save is cancelled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). +* Fixed issue with save button UI, when save is canceled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). * Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). * Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206). * Added setting option for the "send to URL" workflow to switch between caption and alias for the field value's XML element [#1202](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1202) From 0df1f55ddb93a8889f3c1522b7288ff3323b48d8 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:39:30 +0200 Subject: [PATCH 30/38] Update 13/umbraco-forms/release-notes.md --- 13/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index a266afcae3e..026079b4f69 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -29,7 +29,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Resolved duplicate approval occurring when the record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). * Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220). * Fixed issue with save button UI, when save is canceled via a notification [#1219](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1219). -* Improved date format for data values when using the "send email" workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). +* Improved date format for data values when using the **Send email** workflow [#1214](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1214). * Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met [#1206](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1206). * Added setting option for the "send to URL" workflow to switch between caption and alias for the field value's XML element [#1202](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1202) * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221). From 52a2b9e2dea64c997dd87f3465b815447a1879c4 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:39:51 +0200 Subject: [PATCH 31/38] Update 14/umbraco-forms/developer/ajaxforms.md --- 14/umbraco-forms/developer/ajaxforms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/developer/ajaxforms.md b/14/umbraco-forms/developer/ajaxforms.md index 54b629b4b30..ba1e678dab6 100644 --- a/14/umbraco-forms/developer/ajaxforms.md +++ b/14/umbraco-forms/developer/ajaxforms.md @@ -52,7 +52,7 @@ An optional `contentId` parameter can be provided, which can either be the integ A `culture` parameter can also be provided, expected as an ISO code identifying a language used in the Umbraco installation (for example, `en-US`). This will be used to ensure the correct translation for dictionary keys is used. It will also retrieve page content from the appropriate language variant. If the parameter is not provided in the request, the default Umbraco language will be used. -Finally an `additionalData` parameter can be provided in the form of a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). +Finally, an `additionalData` parameter can be provided as a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). If the requested form is not found, a 404 status code will be returned. From f4d1c634005860f5205fa962de02c464fb1ab92f Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:40:16 +0200 Subject: [PATCH 32/38] Update 14/umbraco-forms/developer/extending/setting-types.md --- 14/umbraco-forms/developer/extending/setting-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/developer/extending/setting-types.md b/14/umbraco-forms/developer/extending/setting-types.md index 0cc4c3ee574..6bfc825fa49 100644 --- a/14/umbraco-forms/developer/extending/setting-types.md +++ b/14/umbraco-forms/developer/extending/setting-types.md @@ -30,7 +30,7 @@ Some are defined with the Umbraco CMS and some ship with the Forms package. | Umb.PropertyEditorUi.Integer | CMS | Uses numerical text box for entry | | | Umb.PropertyEditorUi.MultipleTextString | CMS | Uses multiple text boxes for entry | Not used in core types | | Umb.PropertyEditorUi.Slider | CMS | Uses a slider for range input | The "reCAPTCHAv3" field type | -| Umb.PropertyEditorUi.TextArea | CMS | Used a multiline textbox for entry | | +| Umb.PropertyEditorUi.TextArea | CMS | Uses a multiline textbox for entry | | | Umb.PropertyEditorUi.TextBox | CMS | Uses a single-line textbox for entry | | | Umb.PropertyEditorUi.TinyMCE | CMS | Uses a rich text editor for input | The "Send email" workflows | | Umb.PropertyEditorUi.Toggle | CMS | Uses a single checkbox for entry | | From 37d97c7681b6c103bf2311e3c4419a3337fb062b Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:40:47 +0200 Subject: [PATCH 33/38] Update 13/umbraco-forms/release-notes.md --- 13/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 026079b4f69..047cf0e781c 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -39,7 +39,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). * Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). * Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). -* Improved support for editing large, multi-page forms by retaining scroll position between views and adding a "jump to page" option [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1243). +* Improved support for editing large, multi-page forms by retaining scroll position between views and adding a "jump to page" option [#1243](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1243). #### [**13.1.2**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.4) **(April 16th 2024)** From d3a0960b1f95a7347b73a6de09495e194d8b6a40 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:41:20 +0200 Subject: [PATCH 34/38] Update 14/umbraco-forms/release-notes.md --- 14/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index 3bfec844b71..61543db267e 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -19,7 +19,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang #### [**14.1.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) **(July 9th 2024)** -* Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) +* Added setting option for single and multiple choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) * Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic and update within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) From 4f539db40006962a2e88a2f91bf50365481600dc Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 12:42:26 +0200 Subject: [PATCH 35/38] Update 13/umbraco-forms/release-notes.md --- 13/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 047cf0e781c..606bb04af51 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -19,7 +19,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang #### [**13.2.0-rc1**](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.0) **(July 9th 2024)** -* Added setting option for multiple and choice choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). +* Added setting option for single and multiple choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). * Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) * Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210). * Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic and update within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578). From 3c614cd4532dd8c663608544ba82d385de6c7c29 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 14:09:31 +0200 Subject: [PATCH 36/38] Update 14/umbraco-forms/release-notes.md --- 14/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md index 61543db267e..68ae2f6d69c 100644 --- a/14/umbraco-forms/release-notes.md +++ b/14/umbraco-forms/release-notes.md @@ -27,7 +27,7 @@ This section contains the release notes for Umbraco Forms 14 including all chang * Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). -* Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). +* Fixed console error with blank values in the date picker field [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). * Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). * Resolved issues with intermittent failures of the form entries table display [#1239](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1239). From 9d890e9d528959eb8ccd791f8ac83fbdefbd6bc0 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 8 Jul 2024 14:09:42 +0200 Subject: [PATCH 37/38] Update 13/umbraco-forms/release-notes.md --- 13/umbraco-forms/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/release-notes.md b/13/umbraco-forms/release-notes.md index 606bb04af51..98c635eb605 100644 --- a/13/umbraco-forms/release-notes.md +++ b/13/umbraco-forms/release-notes.md @@ -37,7 +37,7 @@ This section contains the release notes for Umbraco Forms 13 including all chang * Fixed issues with retrieving fields and assigning default values when using the datasource wizard. * Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). * Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). -* Fixed console error with blank values in data picker fields [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). +* Fixed console error with blank values in the date picker field [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). * Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). * Improved support for editing large, multi-page forms by retaining scroll position between views and adding a "jump to page" option [#1243](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1243). From 50de533c965b69f93aeee173b1d5f2c06443f8aa Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 9 Jul 2024 07:03:33 +0200 Subject: [PATCH 38/38] Update theme link --- 10/umbraco-forms/developer/themes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10/umbraco-forms/developer/themes.md b/10/umbraco-forms/developer/themes.md index 99c9d923151..5e9b9509abb 100644 --- a/10/umbraco-forms/developer/themes.md +++ b/10/umbraco-forms/developer/themes.md @@ -21,7 +21,7 @@ Umbraco 10+ distributes these files as part of a Razor class library, so you won You can obtain the latest version of the default theme Forms 10 from the following link: -* [Forms 10 Default Theme](https://umbra.co/umbraco-forms-default-theme) (for 10.5.5 and above) +* [Forms 10 Default Theme](https://umbra.co/umbraco-forms-default-theme) (for 10.5.6 and above) If you are using a lower minor version of Forms than those listed, you should download an older version of the default theme.