Products
Packages [expand] [collapse]
Services
Released in version
4.2.1
4.2.0
4.1.0
4.0.2
4.0.1
4.0.0
3.2.0
3.1.0
3.0.0
2.0.1
1.3.2
1.3.0
1.2.1.9000
1.2.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, package, or service in the left menu, and filter for dates, features, or bug fixes.

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

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

Changes in EPiServer.MarketingAutomationIntegration.Silverpop

Item type
From date
To date
Items/Page
Area Id Type Description Released
MAI-1635
  Change name of Silverpop settings page in admin mode to match others

Change the name of settings page for Silverpop from "Silverpop Engage" to "Silverpop Connector," so it matches the other connectors.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.2.1;
Mar 08, 2020
MAI-1761
  SilverPop connector min framework requirement needs upgrade

The connector references a class in the newer version of the framework. This results in the following exception: Could not load type 'Episerver.Marketing.Common.Exceptions.EntityNotFoundException

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.2.1;
Mar 08, 2020
MAI-1544
  Access to 4.x features for email templates

Re-introduce code that allowed customers to customize email templates into Silverpop 5.x connector.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.2.0;
Mar 07, 2019
MAI-1557
  Silverpop: If settings saving fails, tracking script option always set to default
Steps to reproduce

1. Add an invalid value (for example, Engage Pod Number = Engage Pod 4) to an instance of the Silverpop connector.
2. Add valid values to the remaining fields (Connector name and Token).
3. Select the Custom tracking scripts option then enter a text value to the enabling textbox.
4. Click the Save button.

Expected:
Once the settings fail in saving, all entering values and option should remain.

Actual:
Failed for settings saving as expected. But the tracking option is set to the default: "No tracking scripts...."

Test configuration

EPiServer.ConnectForMarketingAutomation.4.1.0-pre-000808
EPiServer.Marketing.Automation.Forms.4.1.0-pre-000808
Episerver.MarketingAutomationIntegration.Silverpop.4.1.0-pre-000808

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.2.0;
Mar 07, 2019
MAI-1372
  Silverpop: Update settings UI to allow creation of multiple instances.
Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
Dec 09, 2018
MAI-1512
  Silverpop: 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.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.1.0;
Dec 09, 2018
MAI-1332
  Webtracking code only adds first connector script found

Since there can be multiple connectors of each type, we need to add the script for each connector of the same type to pages. Currently, the code only adds the first one it finds of each type.

Steps to reproduce
1) Create an Alloy sample site.
2) Install the Silverpop connector and configure it.
3) Select a custom script and enter the text "Connector 1". This text will show up on every page.
4) Programmatically create a new instance of the Silverpop connector. Set the script text to be "Connector 2".
5) View a page.

Expected:
Both custom scripts exist on the page.

Actual:
Only a single copy of the text shows up.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.0.2; EPiServer.MarketingAutomationIntegration.Marketo 4.0.1;
Sep 02, 2018
MAI-1307
  Silverpop form mapping upgrade script may not always correctly remap contact list ids

The length of the contact list id is being calculated incorrectly in rare cases where the database id and contact list id are different lengths.

An update to the script needs to correctly determine the contact list id length. The package also needs to be updated to no longer run the old database upgrade script. This puts the form mapping into a state from which it cannot be recovered.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.0.1;
Jul 22, 2018
MAI-1132
  Create Silverpop Connector

Create Silverpop Connector that uses the new framework.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.0.0;
Jul 01, 2018
MAI-1290
  Automate SilverPop Form mapping upgrade

Update the form mappings for the Silverpop connector. As a result, users can update their connector without having to remap their forms from the old MAI form datasource id to the new MAI form datasource id format.

Fix Version/s: EPiServer.MarketingAutomationIntegration.Silverpop 4.0.0;
Jul 01, 2018
1 2 Next