Packages [expand] [collapse]
Released in version
4.3.0
4.2.1
4.2.0
4.1.0
4.0.2
4.0.1
4.0.0
3.3.0
3.2.0
3.1.0
3.0.1
3.0.0
2.0.0
1.4.1
1.4.0
1.3.1
1.3.0
1.2.2.9000
1.2.1.9000
1.2.0.9000
1.1.1.9000
1.1.0.9000
1.0.8.8000
1.0.7.8000
1.0.6.8000
1.0.5

Release notes for Optimizely updates

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project; see Installing Optimizely updates.

Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.

  • Bug. Display bug fixes.
  • Critical bug. Display only critical bug fixes.
  • Feature. Display only new features (all features).
  • UI Feature. Display only end-user (user interface) features.

Note: NuGet packages listed here may not be immediately available in the Optimizely NuGet feed.

Latest changes

Item type
Filter on date
Items/Page
Area ID Type Description Released
MAI-1886
  Allow user to accept or deny mai_trk_* cookies

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.

EPiServer.ConnectForMarketingAutomation 5.7.0; EPiServer.Marketing.Automation.Forms 2.4.0; EPiServer.Marketing.Connector.Delivra 1.2.0; EPiServer.MarketingAutomationIntegration.Eloqua 4.2.0; EPiServer.MarketingAutomationIntegration.ExactTarget 4.3.0; EPiServer.MarketingAutomationIntegration.HubSpot 4.2.0; EPiServer.MarketingAutomationIntegration.Marketo 4.6.0; EPiServer.MarketingAutomationIntegration.Salesforce 4.3.0; EPiServer.MarketingAutomationIntegration.Silverpop 4.5.0;
Jul 20, 2021
MAI-1827
  Salesforce: When using SOAP API, failed to create leads after a session expired.

When you used SOAP API option in the settings, form submissions failed to create leads after the session expired, and generated the following error:
System.Web.Services.Protocols.SoapException: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash

EPiServer.MarketingAutomationIntegration.Salesforce 4.2.1;
Jun 21, 2020
MAI-1611
  Salesforce: Add option to submit form data asynchronously

Provide an option to allow for asynchronous submission of data to Salesforce. This includes adding a checkbox on the admin settings screen to enable async.
If this option is enabled, data submission is a "fire and forget" operation. That is, we won't get back the entityId and store it in the mai cookie. Therefore, auto-fill and personalization based on Salesforce fields won't work.

EPiServer.MarketingAutomationIntegration.Salesforce 4.2.0;
Apr 21, 2019
MAI-1600
  Salesforce: Replace SOAP API with REST API to communicate with Salesforce objects

Switch to REST API for communicating with Salesforce objects.

EPiServer.MarketingAutomationIntegration.Salesforce 4.2.0; EPiServer.ConnectForMarketingAutomation 5.4.0;
Apr 21, 2019
MAI-1511
  Salesforce: Form and form field mappings lost if database upgraded via web.config settings

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.

EPiServer.MarketingAutomationIntegration.Salesforce 4.1.0;
Dec 09, 2018
MAI-1369
  Salesforce: Update settings UI to allow creation of multiple instances.
EPiServer.MarketingAutomationIntegration.Salesforce 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
Dec 09, 2018
MAI-1474
  Salesforce: Incorrect endpoint used to connect to Sandbox instance.

When sandbox option is chosen in the connector settings, it is incorrectly attempting to connect to the production endpoint, which throws the following error:
Error in Authentication of CredentialsINVALID_LOGIN: Invalid username, password, security token; or user locked out.

EPiServer.MarketingAutomationIntegration.Salesforce 4.0.2;
Oct 08, 2018
MAI-1310
  Salesforce: Object reference error when fetching connector data on site initialization and scheduled job

Salesforce stores the login result object in a request variable. The process of fetching the data in the initialization module and scheduled job occurs in a parallel loop.
If the request for Salesforce data happens in a thread different from the originating one, the HttpContext is null. This results in a null reference exception.

EPiServer.MarketingAutomationIntegration.Salesforce 4.0.1;
Jul 22, 2018
MAI-1071
  Salesforce: Create or update a user's information when a form is submitted multiple times.

If a user submits a Salesforce form multiple times, you can either update that user's existing information, or you can create a new entity (lead, contact, and so on).

EPiServer.MarketingAutomationIntegration.Salesforce 3.3.0;
Feb 04, 2018
MAI-1067
  MAI: Add support for CMS version 11 in MAI Core, Salesforce and Silverpop.
EPiServer.ConnectForMarketingAutomation 4.4.0; EPiServer.Marketing.Automation.Forms 1.4.0; EPiServer.MarketingAutomationIntegration.Salesforce 3.2.0; EPiServer.MarketingAutomationIntegration.Silverpop 3.2.0;
Jan 14, 2018
1 2 Next