Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Packages [expand] [collapse]
Released in version
3.1.3
3.1.2
3.1.1
3.1.0
3.0.0
2.4.2
2.4.1
2.4.0
2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
2.0.0
1.4.3
1.4.2
1.4.1
1.4.0
1.3.1
1.3.0
1.2.1
1.2.0
1.1.9
1.1.8
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.1

Release notes for Optimizely CMS and Customized Commerce updates

Important

Release notes moved to a new location. As of May 15th, 2024, the release notes on the World site no longer receive updates. See Release notes by product on the Optimizely Support site.

Go to your product's release notes page and click Follow to receive an email notification whenever release notes are added.

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.
  • Security - Display only security updates.

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; (Or a related package);
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; (Or a related package);
Sep 01, 2023
MAI-2087
  Error occurred for Episerver.Marketing.Automation.Forms package when custom data source was used

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.

 

EPiServer.Marketing.Automation.Forms 2.4.1; (Or a related package);
Feb 07, 2023
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; (Or a related package);
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; (Or a related package);
Jul 20, 2021
MAI-1851
  Eloqua: When Account Name is a separate contact field, datasources are not displayed.

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.

EPiServer.MarketingAutomationIntegration.Eloqua 4.1.2; EPiServer.Marketing.Automation.Forms 2.3.1; EPiServer.ConnectForMarketingAutomation 5.6.1; (Or a related package);
Oct 20, 2020
MAI-1355
  Form's data cannot be submitted to external system if the first form element is not mapped to any remote field

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

EPiServer.Marketing.Automation.Forms 2.0.1; (Or a related package);
Sep 02, 2018
MAI-1359
  Form Mapping - The main datasource should be listed first in the dropdown.

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

EPiServer.Marketing.Automation.Forms 2.0.1; (Or a related package);
Sep 02, 2018
MAI-1174
  MAI: Error if form fields not mapped to corresponding field(s) in installed connector

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.Marketing.Automation.Forms 1.4.3; (Or a related package);
Apr 22, 2018
MAI-1159
  MAI: Improve caching of forms-MAI integration package

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

EPiServer.Marketing.Automation.Forms 1.4.2; (Or a related package);
Apr 15, 2018
1 2 Next