Release notes for Episerver updates

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.

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.

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

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.

jQuery version on Forms upgraded to 3.5.1.

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">

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.

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.

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.

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.