Release notes for Optimizely CMS and Customized Commerce updates

Added a retry policy to ensure the successful execution of Marketo API requests, even in cases where the number of requests exceeds the maximum rate of 100 requests per 20 seconds. 

Fixed an issue where the Marketo connector incorrectly displayed detailed error information when incorrect credentials were entered on the admin UI. 

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.

Add method to schedule campaigns in the REST Service API.

Form field mapping for custom fields lost when upgrading from 3.x to 4.x.

While attempting to fetch a lead with a large number of fields, the Marketo connector results in an error.
"System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine".

Form and form field mappings are lost if the database is upgraded from 3.x to 4.x via the updateDatabaseSchema attribute of the <episerver.framework> element in the web.config.

Since there can be multiple connectors of each type, we need to add the script for each connector of the same type to pages. Currently, the code only adds the first one it finds of each type.

Steps to reproduce
1) Create an Alloy sample site.
2) Install the Silverpop connector and configure it.
3) Select a custom script and enter the text "Connector 1". This text will show up on every page.
4) Programmatically create a new instance of the Silverpop connector. Set the script text to be "Connector 2".
5) View a page.

Expected:
Both custom scripts exist on the page.

Actual:
Only a single copy of the text shows up.

Steps to reproduce

1. Submit a Marketo form with valid values for FirstName and Email.
2. Re-submit the form on the same browser session (no clearing cache) with a different email address.

Expected:
After step 2, no new leads are created. Only the lead created in 1st step is updated.

Actual:
2 leads are created.