Products
Packages [expand] [collapse]
Services
Released in version
5.6.1
5.6.0
5.5.6
5.5.5
5.5.4
5.5.3
5.5.2
5.5.1
5.5.0
5.4.0
5.3.4
5.3.3
5.3.2
5.3.1
5.3.0
5.2.2
5.2.1
5.2.0
5.1.0
5.0.2
5.0.1
5.0.0
4.4.2
4.4.1
4.4.0
4.3.1
4.3.0
4.2.0
4.1.0
4.0.0
3.0.0
2.5.0
2.4.2.9000
2.4.1.9000
2.3.0.9000

Release notes for Episerver updates

This overview lists changes included in Episerver updates delivered as NuGet packages and services. Use the information to decide which updates to apply to your project, see Installing Episerver updates. Select a product or package, and filter for dates, features, or bug fixes.

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

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

Changes in EPiServer.ConnectForMarketingAutomation

Item type
From date
To date
Items/Page
Id Type Title Released
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.

Version/s: EPiServer.MarketingAutomationIntegration.Eloqua 4.1.2; EPiServer.Marketing.Automation.Forms 2.3.1; EPiServer.ConnectForMarketingAutomation 5.6.1;
Oct 20, 2020
MAI-1819
  Delivra connector: Show the member fields by their display names in form mappings and visitor group UIs.

Delivra Connector: Form field mapping and visitor groups UIs should show display names of fields.

Version/s: EPiServer.ConnectForMarketingAutomation 5.6.0; EPiServer.Marketing.Automation.Forms 2.3.0; EPiServer.Marketing.Connector.Delivra 1.1.0;
Jun 28, 2020
MAI-1758
  Eloqua: Unable to set visitor group criteria with fields that have no value

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.

Version/s: EPiServer.MarketingAutomationIntegration.Eloqua 4.1.1; EPiServer.ConnectForMarketingAutomation 5.5.6;
Mar 08, 2020
MAI-1738
  Silverpop: Visitor group datasource dropdown does not display child contact lists

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.

Version/s: EPiServer.ConnectForMarketingAutomation 5.5.5;
Dec 15, 2019
MAI-1736
  Reduce number of calls to dynamic data store in marketing connector framework.

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

Version/s: EPiServer.ConnectForMarketingAutomation 5.5.4;
Nov 24, 2019
MAI-1728
  Marketing connectors make repeated calls to dynamic data store

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

Version/s: EPiServer.ConnectForMarketingAutomation 5.5.3;
Oct 27, 2019
MAI-1715
  MAI: Odd behavior on connector settings UI

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

Version/s: EPiServer.ConnectForMarketingAutomation 5.5.2;
Oct 20, 2019
MAI-1697
  MAI Global Settings: Unable to save new properties on upgraded sites

The new properties on the global settings UI are not saved when upgrading from EPiServer.ConnectForMarketingAutomation 5.4.0 to 5.5.0.
They work only on a fresh installation of 5.5.0.

Version/s: EPiServer.ConnectForMarketingAutomation 5.5.1;
Sep 10, 2019
MAI-1687
  Option to prevent form submission; display message if submission of form data to connector fails

Currently, if the submission of form data to a marketing connector to create/update an entity is unsuccessful, it logs an error but still shows a success message in the UI. Also, the form submission is recorded in the Epi database.
Provide an option via the Admin settings to choose a different behavior, such that the error is displayed in the UI, and the form submission is not recorded in the database.

Version/s: EPiServer.ConnectForMarketingAutomation 5.5.0; EPiServer.Marketing.Automation.Forms 2.2.0;
Sep 01, 2019
MAI-1600
  Salesforce: Replace SOAP API with REST API to communicate with Salesforce objects

Switch to REST API for communicating with Salesforce objects.

Version/s: EPiServer.MarketingAutomationIntegration.Salesforce 4.2.0; EPiServer.ConnectForMarketingAutomation 5.4.0;
Apr 21, 2019
1 2 3 4 5 6 Next