Products
Packages [expand] [collapse]
Services
Released in version
4.30.2
4.30.1
4.30.0
4.29.3
4.29.2
4.29.1
4.29.0
4.28.0
4.27.1
4.27.0
4.26.0
4.25.1
4.25.0
4.24.3
4.24.2
4.24.1
4.24.0
4.23.0
4.22.0
4.21.0
4.20.0
4.18.0
4.17.0
4.16.0
4.15.1
4.15.0
4.14.1
4.14.0
4.12.0
4.11.0
4.10.0
4.9.1
4.9.0
4.8.5
4.8.4
4.8.3
4.8.2
4.8.1
4.8.0
4.7.0
4.6.1
4.6.0
4.5.1
4.5.0
4.4.4
4.4.3
4.4.2
4.4.1
4.4.0
4.3.0
4.2.2
4.2.1
4.1.0
4.0.1
4.0.0
3.1.0
3.0.0.0
2.1.0.2
2.0.0.2
1.1.4.9000
1.1.2.9000
1.0.0.9000
0.21.1.9000
0.20.0.9000
0.19.4.9000

Release notes for Episerver updates

This overview lists changes included in Episerver updates delivered as NuGet packages and services. Use the information to decide which updates to apply to your project, see Installing Episerver updates. Select a product, package, or service in the left menu, and filter for dates, features, or bug fixes.

  • See only new features (all features) - filter on item type Feature.
  • See only end-user (user interface) features - filter on item type UI Feature.
  • See only critical bug fixes - filter on item type Critical Bug.

Note: New NuGet packages listed here may not be immediately available in the Episerver NuGet feed.

Latest changes

Item type
Filter on date
Items/Page
Area Id Type Description Released
AFORM-2754
  Form field dependencies are not imported correctly

Steps to reproduce:

  1. Create a form with 2 elements and make the second element show if the condition is met on the first element.
  2. Export the page with the form to a file.
  3. Change the name of the first element in the form.
  4. Import the form without updating existing content.
  5. Go to the dependencies tab in the second element of the imported form.
  6. The dependency has a crisscrossed background and the name of the dependent form element is the name of the changed element from the first form. 

Expected result:

Form field dependencies should work.

Actual result:

Dependencies for form elements do not get imported correctly and do not work. In the Dependencies tab in the imported form, the second text element's dependency points to the first text element in the original form.

 

Fix Version/s: EPiServer.Forms 4.30.2;
Jan 19, 2021
AFORM-2579
  Slow ExpiredFormSubmissionRemoveJob

The ExpiredFormSubmissionRemoveJob loads all existing forms before performing a delete action on expired forms. This may cause performance issues if there are a lot of submitted forms.

Fix Version/s: EPiServer.Forms 4.30.1;
Jan 12, 2021
AFORM-2749
  Improve Form submit events

Submitted form events have been updated to support doing asynchronous calls before submitting data.

Fix Version/s: EPiServer.Forms 4.30.1;
Jan 12, 2021
AFORM-2538
  validate method should always return boolean/Deferred

Previously, custom FormContainers that used ChoiceItemWithSelection could fail during submit when the validate method did not return a value. The method now always returns a value.

Fix Version/s: EPiServer.Forms 4.30.0;
Dec 08, 2020
AFORM-2610
  jQuery Core 3.0 Upgrade

jQuery version on Forms upgraded to 3.5.1.

Fix Version/s: EPiServer.Forms 4.30.0;
Dec 08, 2020
AFORM-2536
  Generating a report is saved on disk instead of in blob can cause problems for non-sticky load balanced environment

The problem is when generating a report specificly the call

https://www.abc.se/EPiServer/EPiServer.Forms.UI/DataExporting/PrepareExport

It saves the file to the disk using Path.GetTempPath() eg the systems temp path. That means that the callback in a non sticky load balanced enviroment most likely will hit another instance when trying to get the file.

A good option for where to save it is in the blob storage if there is one configured.

In order to use Azure blob storate
1. Add config to web.config

<episerver.framework>
  <blob defaultProvider="azureblobs">
      <providers>
        <add name="azureblobs" type="EPiServer.Azure.Blobs.AzureBlobProvider,EPiServer.Azure"
              connectionStringName="EPiServerAzureBlobs" container="mycontainer"/>
      </providers>
  </blob>
...

2. In Forms.config add setting to use the provider

<episerverforms dataExportBlobProviderName="azureblobs">

Fix Version/s: EPiServer.Forms 4.29.1;
Jun 30, 2020
AFORM-2450
  Default placeholder text displayed instead of entered text in multi-step forms

When a visitor enters rich text in the place of a placeholder in multi-step forms, the entered text is usually displayed in the next step of the form. In some cases, this can cause performance issues. Select Disable placeholders replacement in the Settings tab of rich-text form elements to not display entered text in the following step. Instead, the default placeholder text will be displayed.

Fix Version/s: EPiServer.Forms 4.29.0;
May 06, 2020
AFORM-2524
  In Readonly mode, hide Reset button on Mapping tab

Steps to reproduce:
1. Install Forms and add some external systems (MAI connectors, etc.).
2. Create a new form.
3. Map the form to an external data source.
4. Publish the form.
5. Create a Swedish version of the form.
6. Edit the Swedish version of the form.
7. Go to the Mapping tab.

Expected:
Hide or disable the Reset button.

Actual:
The Reset button looks disabled, but you can still click it.

Fix Version/s: EPiServer.Forms 4.29.0;
May 05, 2020
AFORM-2310
  Form elements not rendered properly in view mode

Steps to reproduce

1. Add a selection element named "Country" then enter several countries (Sweden, Vietnam).
2. Add the second selection element named "Sweden" then enter some data.
3.Go to the Dependencies tab of the second selection element, add a condition:
Field = country, Operator = Equals, Value = Sweden.
4. Loop through steps 2 and 3 for the "Vietnam" option.
5. Save and publish everything.
6. Go to View mode.

Expect:
All dependency elements should be invisible.

Actual:
Selection elements appear for 1 second and are then hidden.

Fix Version/s: EPiServer.Forms 4.28.0;
Mar 31, 2020
AFORM-2469
  Improve Form element to fullfill the WCAG 2.0 level AA compliance

According to the discussion at https://www.yammer.com/emvp/#/threads/show?threadId=1083938207

We need to improve form element behavior, such as input validation, so the user can fix any errors.

  • If there is an error when submitting, set the input element's aria-invalid attribute = true.
  • Add the input element's aria-describedby attribute to the validation error message.
  • Added the alt attribute to some Img elements.
  • Removed the placeholder attribute if it is empty.
  • Fixed the tab order of the ImageChoiceElement so the validation works.
  • If the submit action fails, the image is focused as it is at the first invalid element.
Fix Version/s: EPiServer.Forms 4.28.0;
Mar 31, 2020
1 2 3 4 5 6 Next