Get an overview of the changes and fixes in each version of Umbraco Forms.
In this section, we have summarized the changes to Umbraco Forms released in each version. Each version is presented with a link to the Forms issue tracker showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail.
If there are any breaking changes or other issues to be aware of when upgrading they are also noted here.
If you are upgrading to a new major version, you can find information about the breaking changes in the Version Specific Upgrade Notes article.
This section contains the release notes for Umbraco Forms 13 including all changes for this version.
All items detailed under release candidates for 13.3.0.
Fixed issue with validation for invalid file extension on form submissions via the API #1310.
Multi-step forms
The 13.3 release of Forms contains features that can improve the user experience of completing multi-page forms.
We have added the option for editors to choose to display paging details on the forms. This will allow those completing forms to get a better understanding of progress as well as see details of the pages still to be completed. #281 #648.
These options are enabled and configured by editors in the Forms settings section on a per-form basis. We also provide a configuration-based toggle for the feature as a whole. In this way, editors can be given access to use the feature only once the styling or theme is prepared.
Ship themes in Razor Class Libraries
Forms ships it's themes and email templates as part of a razor class library for ease of distribution. With this release we make that feature available to your own custom themes and templates (or those created by package developers) #795.
Date picker field type
We have made a couple of updates to the Date Picker field type. The format for the field can now be provided in configuration #1276. And you can now override and localize the aria-label provided for assistive technologies such as screen readers #1082.
Finer grained entries permissions
To allow finer control over editor permissions, we have introduced a "delete entries" setting for users and user groups. Thus you can now give editors explicit permissions to view, edit, or delete entries #1303.
Other
Other bug fixes included in the release:
Fixed issue with single checkbox triggering a condition on a field on a subsequent page #1304.
Improved cross-platform check when exporting to Excel.
Fixed issue where sensitive data flag on a field could not be set for new fields added to a form #1309.
Handled "chunked" authentication cookie in protection of file uploads saved in the media file system #11.
Fixed regression in 13.2.2 that caused validation to fire on the wrong form when multiple forms are hosted on a single page #1297.
Fixed regression in 13.2.0 that prevented a form submission from saving if a workflow approved the entry #1293.
Added check to migration step that adds a property to the forms macro, such that it will avoid an exception if the property already exists #1292.
Added file name validation to file uploads, rejecting files with invalid colon characters #1295.
Used localized label for submit workflow summary heading #1273.
Removed autocomplete on field previews #1271.
Added configurable field level rendering of reCAPTCHA 3 validation result #1277.
Fixed validate and submit script to handle additional markup around submit buttons #1280.
Fixed incorrect concatenation of field CSS classes #1284.
Added server-side validation of configured maximum length for short and long answer fields.
Restored provision of field values in HTTP headers in Post as XML workflow.
Fixed issue with recording of form submissions in custom Examine indexes #1282.
Added ability to retrieve "slim" workflow entities from services #1283.
Fixed issue with entries export for Windows installations without access to a component necessary for auto-fit of Excel columns #1259.
The 13.2.0 release contains minor changes to the mark-up in the following Razor files shipped with the product: Form.cshtml, FieldType.RadioButtonList.cshtml, and FieldType.CheckBoxList.cshtml. These changes were made to resolve issues #1220 and #1218.
Please ensure to check the rendering of these features on website forms after the upgrade. If you need to view the files to compare changes, you can download and view the latest and previous versions.
All issues from earlier 13.2 release candidates.
Ensured prevalues can be retrieved outside of an HTTP request context when they depend on a static root node #1258.
Allowed users without sensitive data permissions to set, but not remove, the sensitive flag on a form field #1233.
Ordered select list of prevalue sources when defining prevalues for a form field.
Limited the field preview for a field containing prevalues.
Added setting option for single and multiple choice fields to allow for vertical or horizontal display #1218.
Added new setting type for multiple text strings #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.
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. The data will be associated with the created record and made available for custom logic and update within workflows. #578.
Added details of workflow type to edit workflow dialog #1183.
Removed an inline prevalue editor that wasn't functional but could surface it's UI when creating forms from templates #1230.
Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions #1227.
Resolved duplicate approval occurring when the record is approved via a workflow #1223.
Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden #1220.
Fixed issue with save button UI, when save is canceled via a notification #1219.
Improved date format for data values when using the Send email workflow #1214.
Removed unnecessary circular checks for conditions on workflows resolving an issue where workflow would trigger when conditions were not met #1206.
Added setting option for the "send to URL" workflow to switch between caption and alias for the field value's XML element #1202
Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview #1221.
Restored target used to generate local configuration schema information #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.
Added body rich text field for send email with Razor template workflow #1198.
Fixed console error with blank values in the date picker field #1241.
Ensured placeholders are parsed for accepted entry response from the delivery API #1238.
Improved support for editing large, multi-page forms by retaining scroll position between views and adding a "jump to page" option #1243.
Corrected alignment of label for and input id attributes in the date picker field #1200.
Corrected permission check such that users with only "view entries" permissions can see form details on the dashboard #1192.
Used requestSubmit when submitting forms #1199.
Tightened path check used in middleware for restriction of access to form file uploads.
Fixes regression issue with form validation where two forms are rendered on a single page #1189.
With the introduction of webhooks in Umbraco 13, we've made an update to Forms to allow workflow execution events to trigger webhooks. Workflows are operations that you can associate with form submission, approval, or rejection actions. You can use these where you need to notify external systems of the success or failure of a workflow. Read more on Umbraco Forms Webhooks.
We've added an update that will help customers using Forms within locked down production environments.
And there are a couple of further additions to improve the performance and accessibility of the product.
Features implemented and issues resolved in 13.1.0
Added webhooks for workflow execution events #1151.
Added support for a proxied request when using reCAPTCHA 3 #1159.
Added a cachebuster querystring based on the current product version to rendered script dependencies #773.
Ensured that client-side conditions logic correctly implements "is" with multiple values, such that the condition passes if one and only one matching value is found #1173.
Fixed closing of theme picker dialog #1174.
Fixed rendering of translated dictionary items used for form captions #1175.
Applied multiple click protection for form submissions for installations using the aspnet-validation library #1182.
Ensured UI for the upload of a text file for a prevalue source only allows the selection of expected .txt files.
Handled potential null value for prevalues for a form definition following an upgrade #1157
Fixed handling of API and traditional form posts in reCAPTCHA 3 checks #1150
Fixed display of validation error when a duplicate form field alias is created #1152
Fixed issue where file uploads weren't removed as records were deleted.
Updated Microsoft.Data.SqlClient dependency due to reported security advisory.
Added configuration value TitleAndDescription:AllowUnsafeHtmlRendering to allow tighter security for HTML rendering of text entered in the "Title and description" field type.
See further details on the configuration page.
Rendered dictionary translations of field captions in backoffice entries view #1131.
Ensured valid format string before rendering validation methods with placeholders #1132.
Ensured the creation of the forms to content relation type is idempotent and created with consistent GUID #1137.
Ensured Examine re-index user interface completes when no records are available for indexing #1137.
Fixed issue where use of a custom field HTML ID attribute prefix breaks conditional logic in multi-page forms #1138.
Added support for record based magic string replacement in the post-submission message #1133.
Tightens up the null checks when reading form definition JSON for prevalue captions #1140.
Added configuration value DisableRelationTracking to allow relation tracking between forms and content to be disabled.
See further details on the configuration page.
Added configuration value TrackRenderedFormsStorageMethod to allow use of HttpContext.Items over TempData when tracking rendered forms #1144.
See further details on the configuration page and the rendering scripts page.
Resolved an out of range exception when a condition hides all fields on the final page of a multi-page form.
Fixed issue with swapping between plain and rich text when configuring the post-submission message #1145.
Compatibility with Umbraco 13
See full details of breaking changes under the version specific upgrade guide.
Ran registered server-side file validators on file uploads.
Added migrator to support changes in Form field prevalues when importing from older Umbraco versions
You can find the release notes for versions out of support in the Legacy documentation on Github and Umbraco Forms Package page.