Release notes for Optimizely CMS and Customized Commerce updates

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.

The MAI connectors store entity data in a cache with a sliding expiration of 10 minutes.
This causes an issue where if the data is updated directly on the provider portal itself (as opposed to updating via form submission), it won't be reflected on personalized blocks and form auto-fill unless the cache is not accessed in the cache expiration interval of 10 minutes.

This behavior has been changed from version 5.6.3, by setting the cache to expire after a fixed interval of 10 minutes.

When you configured a visitor group, an error occurred if duplicate field names were present in the marketing provider.

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.

In the Eloqua connector, for a contact, only fields with a value are being returned. As a result, visitor groups with a criterion based on a field not having a value (for example, Null or Empty) are not matched correctly.

The datasources dropdown on the Visitor Group Profile Criteria configuration screen for Silverpop lists only parent level databases. The dropdown should also display child contact lists.

There are multiple calls to dynamic data store to fetch the connector credentials. Use caching to reduce the number of calls.

There are multiple calls to dynamic data store to fetch the list of active connectors. Use caching to reduce the number of calls.

Steps to reproduce
1) Go to any connector's Admin settings screen, for example, Admin -> Config -> Microsoft Dynamics CRM.
2) Add settings and save.
3) Refresh the page.
4) Click Add Connector. An empty settings box appears.
5) Without saving anything, click the Microsoft Dynamics CRM link in the left navigation. The empty settings box remains on the screen.
6) Click the "Microsoft Dynamics CRM" link again. The empty settings box disappears.

Expected
The empty settings box disappears after the first click on the Microsoft Dynamics CRM link.
Also, after the first click, when the empty settings box remains on the screen, if valid values are entered and "save" button is clicked, the box disappears, leaving only the previously saved settings box on the screen. That is, the new instance is not saved.

Actual
See steps to reproduce