Release notes for Optimizely CMS and Customized Commerce updates

Fixed an issue that could cause a crash if an excessive number of login requests occur, such as invalid saved credentials become invalid (due to expired password, security token reset and so on); the login request to Salesforce fails and throws an exception with the message "invalid_grant".

Fixed an issue in the Salesforce connector, which was making an excessive number of authentication calls when credentials became invalid.

Fixed an issue on a site where Episerver.Marketing.Automation.Forms package was installed: if you tried to fetch the form field values for auto-fill when a custom data source was used to map form fields, an error occurred.

Upgraded the following marketing automation connectors to support Optimizely Content Cloud version 12 (CMS 12). 

• Acoustic (Silverpop)
• Delivra
• Eloqua
• Marketo
• Microsoft Dynamics CRM
• Salesforce
• Salesforce Marketing Cloud (ExactTarget)

The following connectors will be released at a later date.

• Hubspot
• Pardot

In accordance with GDPR regulations, you can choose whether you want to accept cookies for Marketing Automation connectors. (Normally, the cookie is created when you submit a marketing automation form.)

Customers are responsible for presenting the cookie option dialog box to the user, obtaining the response, and then passing the response to Optimizely through the IPersonalizationEvaluator.AcceptCookies property. If the user chooses not to accept the cookies, some or all functionality of the connector will not work; the form will post successfully but personalization features will not.

In Eloqua, the Company field is mapped to the accountName parameter. If you have both Company and accountName fields in your Eloqua instance, an error occurs.

Note: To map a form field to Company, use the accountName field from the datasources dropdown.

Steps to reproduce:

1. Create a form and map it with a remote datasourse:

2. Add some fields to the form and map them to corresponding fields in the remote datasource, EXCEPT the first field:

3. Add the form to a page, then open the page and submit the form.

Actual result: Form's data is not submitted to the external datasource
Expected result: Form's data is submitted to the external datasource

Currently, the submission targets are listed first followed by the main datasource. It should be the other way around.

Steps to reproduce:

1. Set up the automation connector (with "Enable Auto-fill on forms" turned on).
2. Create an Episerver form that connects to the Contact table.
3. Set up field mapping.
4. Input sample data and submit.
5. See data sent to Hubspot.
6. Drag more form elements to the form, use settings by default, no field mapping setting.
7. Open the page that contains the form in view mode.

Expected: The page opens as normal.

Actual: The page shows an exception.

Note: The form works normally if "Enable Auto-fill on forms" is turned off.

Episerver made improvements to the performance and caching of MAI connectors.