You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Rendered a hidden submit button on multi-page forms. Ensures that a default button to go forward is used when submitting a form via return key press or a mobile "Go" button [#1343](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1343).
* Used the name and description defined on the setting attribute for backoffice labels when no client-side localization is available [#1336](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1336).
38
-
* Resolved minor backoffice issues when creating and saving prevalue and data sources.
39
-
* Resolved issue where maximum length check on input field was applied to incorrect field [#1342](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1342).
When creating forms you are able to add validation to individual fields, making them mandatory or applying a regular expression pattern. With the 13.4 release we are looking to make this more powerful, by allowing the addition of validation rules for the entire form. The idea is that this will allow you to validate expressions based on multiple fields. For example, "these two email fields should be the same", or "this date should be after this other one".
46
-
47
-
Crafting these rules requires use of [JSON logic](https://jsonlogic.com/) so is considered a "power user" feature. They also require an additional front-end dependency for the rendering of forms on the website. As such they are surfaced on a new "Advanced" tab and only visible and used if enabled in configuration. We don't have, and it seems difficult to provide, an intuitive user interface for rule creation taking into account all the flexibility available. Nonetheless, having the ability to use more complex validation rules seems a valuable addition.
48
-
49
-
When the form is rendered, the validation rules will be applied on the client, where we support both the `aspnet-client-validation` and `jquery.validate` libraries. They are also verified server-side. In this way you can ensure the submission is only accepted if it meets the requirements.
50
-
51
-
Feedback on this feature in particular is welcome.
52
-
53
-
Read more about [editing advanced validation rules](./editor/creating-a-form/form-advanced.md) as well as the [configuration option required to enable them](./developer/configuration/README.md#enableadvancedvalidationrules).
54
-
55
-
#### Tracking editor activity
56
-
57
-
Whilst previously we tracked and displayed the date a form was created and last edited, we didn't show who had made these updates. With 15.1 installed we will start to track this and display the information where available. You'll find this on the form, data source or prevalue source's "Info" tab [#1315](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1315).
58
-
59
-
#### Copy of workflows
60
-
61
-
Forms allows you to make a copy of a form to use as a starting point for a new one. You can choose whether or not to copy workflows along with the form. With the 15.1 release, we've made available a second dialog allowing you to copy workflows to an existing form [#1185](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1185). You can select any or all of the workflows on the current form and copy them to the selected destination form.
62
-
63
-
We've also resolved an edge case around copying a form. It's possible to [define workflows as mandatory](./developer/extending/customize-default-workflows.md#setting-a-mandatory-default-workflow). Copying the form without workflows excludes the desired workflow. You would have a form that didn't contain the workflow you wanted to be included on all. This has been tightened up now and mandatory workflows will always be assigned to the copied form [#1331](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1331).
64
-
65
-
#### File upload validation messages
66
-
67
-
Previously the validation messages presented on the website front end when uploading files were hardcoded and always provided in English. We've added settings now to the "File Upload" field type allowing you to customize these. Dictionary keys can be used in order to provide the information in the user's preferred language [#1327](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1327).
68
-
69
-
#### Other
70
-
71
-
Other bug fixes included in the release:
72
-
73
-
* Fixed issue with applying links to rich text settings on custom field or workflow types [#1329](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1329).
* Fixed regression introduced in 15.0.1 that caused issues for custom field types overriding the `ProcessSubmittedValue` method [#1328](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1328).
* Fixed issues with multi-page forms used in conjunction with a `FormPrePopulateNotification` handler. File uploads and multi-value fields like checkbox lists now function correctly [#1317](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1317)[#1320](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1320).
89
-
* Added a couple of missing translation keys [#1316](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1316)[#1319](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1319).
90
-
* Rendered file upload previews in the backoffice.
91
-
* Fixed issue with saving the "Hide field validation labels" value when editing form settings.
92
-
* Fixed issue with selection of Document Type on the "Save as Umbraco node" workflow type.
93
-
* Used correct labels for conditions when used on fields, fieldsets, pages or workflows [#1323](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1323).
* Preview of features and bug fixes due in 13.3 and 14.2:
107
-
* Fixed issue where sensitive data flag on a field could not be set for new fields added to a form [#1309](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1309)
108
-
* Added date picker setting to set the text for the aria-label [#1082](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1082)
109
-
* Allow selection of custom fields for values and captions for pre-value sources based on Umbraco documents [#1195](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1195)
110
-
* Added Umbraco Flavoured Markdown component for the rendering of form names within a block list
111
-
* Added validation message when submitting a form via the API with an invalid file extension [#1310](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1310)
* Preview of features and bug fixes due in 13.3 and 14.2:
117
-
* Permission for delete entries [#1303](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1303).
118
-
* Configurable date format for date picker field [#1276](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1276).
119
-
* Fixed issue with single checkbox triggering a condition on a field on a subsequent page [#1304](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1304).
120
-
* Improve cross-platform check when exporting to Excel.
* See full details of breaking changes under the [Version-specific Upgrade Guide](upgrading/version-specific/).
126
-
* Made retrieval of prevalue source values and execution of record exports asynchronous [#1285](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1285).
127
-
* Preview of features due in 13.3 and 14.2:
128
-
* Option to display paging details for multi-page forms.
129
-
* Form picker with allowed forms managed via folders.
130
-
* New "form details picker" providing a single property editor for the selection of form, theme, and redirect.
131
-
* Ability to provide custom themes and email templates via razor class libraries [#795](https://github.com/umbraco/Umbraco.Forms.Issues/issues/795).
132
-
* Backoffice translations for Dutch [#1264](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1264).
133
30
134
31
## Umbraco.Forms.Deploy
135
32
136
33
This Deploy add-on adds support for transferring, restoring, exporting and importing (including migrating between major versions) of Umbraco Forms data.
137
34
138
-
### 15.1.0 (January 23rd 2025)
139
-
140
-
* All items from 15.1.0-rc1
141
-
142
-
### 15.1.0-rc1 (December 17th 2024)
143
-
144
-
* Set the form entities created/updated by to the resolved user when deploying (requires Umbraco Forms 15.1)
145
-
146
-
### 15.0.0 (November 14th 2024)
147
-
148
-
* Update Forms and Deploy dependencies to 15.0.0
149
-
150
-
### 15.0.0-rc4 (November 13th 2024)
151
-
152
-
* Update Forms and Deploy dependencies to 15.0.0-rc4
153
-
154
-
### 15.0.0-rc3 (November 7th 2024)
155
-
156
-
* Update Forms and Deploy dependencies to 15.0.0-rc3
157
-
158
-
### 15.0.0-rc2 (October 24th 2024)
35
+
### 16.0.0-rc2 (May 30th 2025)
159
36
160
-
* Update Forms and Deploy dependencies to 15.0.0-rc2
37
+
* Update Forms and Deploy dependencies to 16.0.0-rc2
38
+
* Update client-side entity types to align with server-side (UDI entity types)
161
39
162
-
### 15.0.0-rc1 (October 14th 2024)
40
+
### 16.0.0-rc1 (May 20th 2025)
163
41
164
-
* Update Forms and Deploy dependencies to 15.0.0-rc1
42
+
* Update Forms and Deploy dependencies to 16.0.0-rc1
Copy file name to clipboardExpand all lines: 16/umbraco-forms/upgrading/version-specific.md
+7-33Lines changed: 7 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,51 +6,25 @@ description: >-
6
6
7
7
# Version Specific Upgrade Notes
8
8
9
-
This article provides specific upgrade documentation for migrating to Umbraco Forms version 15.
9
+
This article provides specific upgrade documentation for migrating to Umbraco Forms version 16.
10
10
11
11
{% hint style="info" %}
12
12
If you are upgrading to a minor or patch version, you can find the details about the changes in the [Release Notes](../release-notes.md) article.
13
13
{% endhint %}
14
14
15
15
## Version Specific Upgrade Notes History
16
16
17
-
Version 15 of Umbraco Forms has a minimum dependency on Umbraco CMS core of `15.0.0`. It runs on .NET 9.
17
+
Version 16 of Umbraco Forms has a minimum dependency on Umbraco CMS core of `16.0.0`. It runs on .NET 9.
18
18
19
-
#### **Breaking changes**
19
+
###Breaking changes
20
20
21
-
Version 15 contains a number of breaking changes. If you do run into any, they should be straightforward to adjust and recompile.
21
+
Version 16 contains a number of breaking changes. If you do run into any, they should be straightforward to adjust and recompile.
22
22
23
23
For reference, the full details are listed here:
24
24
25
-
#### **Configuration**
26
-
27
-
* The setting `FieldSettings:Recaptcha3:ShowFieldValidation` has a new default of `true`.
28
-
* The setting `Options:EnableMultiPageFormSettings` has a new default of `true`.
29
-
* The setting `FormDesign:RemoveProvidedEmailTemplate` has been removed (as adding and removing email templates can be more consistently handled using [`EmailTemplateCollection`](../developer/themes.md#removing-the-default-email-template)).
30
-
31
-
#### **Asynchronous Methods**
32
-
33
-
*`IFieldPreValueSourceType.GetPrevalues` (and the abstract method of the same name in `FieldPreValueSourceType`) is now an asynchronous method. It has an `Async` suffix.
34
-
*`IExportType.ExportRecords` and `ExportToFile` are now asynchronous methods and have `Async` suffixes.
35
-
36
-
#### **Code**
37
-
38
-
* Parameters in the `FileUpload` constructor were renamed.
39
-
* Obsolete constructors in the classes `SendRazorEmail`, `EntryAcceptedDtoFactory`, `FormDtoFactory`, `RenderFormViewComponent`, `GetValuesByKeyPrevalueSourceController`, and `UmbracoFormsController` were removed.
40
-
* The obsolete overload on `FormFileExtensions.IsFileTypeAllowed` was removed.
41
-
* The purposes defined for uses of `IDataProtector` were renamed to have a common prefix.
42
-
* Unused fields `Field.Placeholder` and `FormFieldDto.Placeholder` were removed.
43
-
* Unused `ServerVariablesParsingHandler` was removed.
44
-
* Default implementations on the interfaces `IWorkflowFactory`, `IWorkflowRepository`, `IWorkflowService` were removed.
45
-
* Obsolete methods on `PlaceholderParsingService` were removed.
46
-
* Method overloads without optional parameters on `FormDtoFactory`, `EntryAcceptedDtoFactory`, `IFormRenderingService`, `IPlaceholderParsingService`, `WorkflowType`, `DictionaryExtensions` and `StringExtensions` were removed.
47
-
* Base64 encoding was removed when storing and retrieving form state.
48
-
* The obsolete overload of `FormViewModel.Build` was removed.
49
-
* The `UmbracoPreValuesReadOnly` constructor now has an additional parameter.
50
-
* Due to the introduction of asynchronous behavior to `IFieldPreValueSourceType.GetPrevalues`, `FormViewModel.Build` is now also asynchronous.
51
-
*`FormsTreeRequirement` and related classes were removed.
52
-
*`FormRenderingService` and `FormThemeResolver` was made internal.
53
-
* Default implementations on `IFormThemeResolver` were removed.
25
+
#### Removed EPPlus dependency
26
+
27
+
Previous versions of Forms depended on EPPlus version 4, the last LGPL-licensed release, which is no longer supported. Newer versions require a commerce license, which is not desired for built-in Forms features (such as exporting form entries to formatted Excel files). The built-in export now uses CsvHelper to generate CSV files instead.
0 commit comments