Our monthly Virtual Happy Hour is happening this week, Fri Feb 23!

Try our conversational search powered by Generative AI!

Packages [expand] [collapse]
Released in version
5.1.3
5.1.2
5.1.1
5.1.0
5.0.0
4.3.3
4.3.2
4.3.1
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 CMS and Customized Commerce updates

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

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-2133
  CMS 12 Salesforce: Excessive failed login attempts.

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".

EPiServer.Marketing.Automation.Forms 3.1.3; EPiServer.MarketingAutomationIntegration.Salesforce 5.1.3; EPiServer.ConnectForMarketingAutomation 6.1.4;
Oct 03, 2023
MAI-2129
  CMS 11 Salesforce: Excessive failed login attempts.

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

EPiServer.MarketingAutomationIntegration.Salesforce 4.3.3; EPiServer.ConnectForMarketingAutomation 5.7.1; Episerver.Marketing.Automation.Forms 2.4.2;
Sep 01, 2023
MAI-2093
  Salesforce connector: Access token not updated in cache after re-authenticating, when session ID expires.

Fixed an issue that did not update a token in the cache when the session ID expired and used an expired token to retry authentication.

EPiServer.MarketingAutomationIntegration.Salesforce 4.3.2;
Mar 14, 2023
MAI-2018
  Salesforce connector does not allow certain special characters (like "&") in username and password.

Fixed an issue where the Salesforce connector failed to authenticate when the ampersand ( & ) and plus ( + ) special characters were included in username and password. 

EPiServer.MarketingAutomationIntegration.Salesforce 4.3.1;
Dec 20, 2022
MAI-1893
  Upgrade marketing automation connectors to .NET 5

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
EPiServer.MarketingAutomationIntegration.MSDynamics 6.0.0; EPiServer.MarketingAutomationIntegration.Silverpop 5.0.0; EPiServer.MarketingAutomationIntegration.Salesforce 5.0.0; EPiServer.MarketingAutomationIntegration.Marketo 5.0.0; EPiServer.MarketingAutomationIntegration.ExactTarget 5.0.0; EPiServer.MarketingAutomationIntegration.Eloqua 5.0.0; EPiServer.Marketing.Connector.Delivra 2.0.0; EPiServer.Marketing.Automation.Forms 3.0.0; EPiServer.ConnectForMarketingAutomation 6.0.0;
Dec 21, 2021
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-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-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
1 2 Next