Release notes for Optimizely CMS and Customized Commerce updates

Steps to reproduce

1. Create a page with a ContentArea.
2. Click a Create a new block link.
3. Select a Form container --> "New Block: Form container" page opens.
3. Dnd the element to the Form Container.
4. Click the Create button.
5. Open the form's Mappings tab.
6. Select Connect to Datasource.
7. Open the added element's Extra field mapping tab.

Expected:
You can map the external system field.

Actual:
External system field mapping is blank, and you cannot map it.

When a form is mapped to an external source, the Datasources property in IExternalSystem and GetSuggestedValues method in IAutofillProvider gets called 3 times for every field on the form, when it loads. Though we cache data we fetch from connectors, it adds a lot of overhead when there is a large number of datasources and/or large number of fields on a form.

To address this, we reduced calls to the Datasources property in IExternalSystem and GetSuggestedValues method in IAutofillProvider to only one time for each field, instead of 3 times as is done currently.

We also improved the performance of the IAutofillProvider implementation by getting all suggested values of all fields at the first call then caching them for late use.

Steps to reproduce

1. Install an external connector: Campaigns Connector.
2. Configure its settings.
3. Create a form.
4. Map Connect to DataSource = a recipient > Publish.
5. DnD 2 textbox elements.
6. Map the first element to "Email" > Publish.
7. Open the external mapping of the second element.

Expected:
Email is not displayed on the list.

Actual:
Email displays and can be selected.

Steps to reproduce

1. Install Language Manager and Forms.
2. Create a form in Svenska(master) and Francaise.
3. Enable the English language for the form.
4. Open the form in English.
5. Select 'Compare with master language' from the Francaise language.
6. Close Compare View.

Expected:
Elements display on Forms Elements.

Actual:
Form Elements gadget opens and is blank.

1. Override DataSubmissionService

public class CustomDataSubmissionService: DataSubmissionService
    {
        protected override Submission GetSubmissionData(NameValueCollection rawSubmittedData, FormContainerBlock formContainer, HttpContextBase httpContext, bool isFinalized)
        {
            var result = base.GetSubmissionData(rawSubmittedData, formContainer, httpContext, isFinalized);
            result = base.GetSubmissionData(rawSubmittedData, formContainer, httpContext, isFinalized);
 
            return result;
        }
    }

2. In initialization module (DependencyResolverInitialization.cs)

context.Services.AddSingleton<DataSubmissionService, CustomDataSubmissionService>();

3. Create a form with UploadFile.
4. Try to submit the form with upload file > File is saved twice (one is empty).

Previously, Episerver Forms did not handle submission actor’s result (actors actually returned results but they were not used).
This feature allows actors to:

• Return signal to cancel form submission in case actor running fails
• Return error message which can be displayed to visitors
  There are some changes when implementing actors in order for the above to work:
  1. Actors must implement ISyncOrderedSubmissionActor. Actors implementing this interface will run synchronously in ascending order, regardless of IsSyncedWithSubmissionProcess value (we force the actor to run synchronously because we cannot control the result of async actors).
  2. Actors must return object instance of a class which implements EPiServer.Forms.Core.PostSubmissionActor.Internal.ISubmissionActorResult.
  By implementing this interface, the returned result will have two properties:
• CancelSubmit (boolean): determine whether the form submission should be canceled or not.
• ErrorMessage (string): this error message will be displayed to visitors.

The Form container has 3 view modes:

• On-Page Editing
• All Properties
• Form submissions

The first two are used to change the form, while the last is used to manage submissions. They are displayed similarly in the dropdown.

In the Commerce Catalog page, an entry can have several view modes, similar to Forms. Here, a line is used to separate the edit view modes (On-Page Editing and All Properties) from other view modes.

The form view mode dropdown should also have this line because it shows that there are differences between Form Submissions from other view modes. It increases consistency between Form UI and Commerce Catalog UI.