Products
Packages [expand] [collapse]
Services
Released in version
4.1.1
4.1.0
4.0.1
4.0.0
3.2.1
3.1.0
3.0.0
1.3.2
1.3.0
1.2.2.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.HubSpot

Item type
From date
To date
Items/Page
Area Id Type Description Released
MAI-1846
  Hubspot: Add Content-type header to the requests made to endpoint.

Update the Hubspot connector to place a content-type header in POST and PUT requests.

Fix Version/s: EPiServer.MarketingAutomationIntegration.HubSpot 4.1.1;
Oct 18, 2020
MAI-1508
  Hubspot: 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.HubSpot 4.1.0;
Dec 09, 2018
MAI-1373
  HubSpot: Update settings UI to allow creation of multiple instances.
Fix Version/s: EPiServer.MarketingAutomationIntegration.HubSpot 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
Dec 09, 2018
MAI-1470
  Hubspot: Data not updated if form submitted second time with same email

When a form mapped to Hubspot is submitted, it is only successful the first time. Subsequent submissions with the same email value are not successful.

Fix Version/s: EPiServer.MarketingAutomationIntegration.HubSpot 4.0.1;
Oct 07, 2018
MAI-1127
  Create HubSpot Connector

Create Connector that uses the new framework.

Note: After upgrading the MAI package, the form may display 2 dropdown lists for selecting the mapping.
This occurs because, after the HubSpot connector updates the name of the .dll file around the MAI framework and you publish the site to another location (such as to the cloud or an IIS site), the old .dll file is not automatically deleted.

To remove the old.dll:

  1. Go to the Publish dialog.
  2. Click the Settings tab.
  3. Under File Publish Options, check Remove additional files at destination.
Fix Version/s: EPiServer.MarketingAutomationIntegration.HubSpot 4.0.0;
Jul 01, 2018
MAI-1286
  Automate HubSpot form mapping upgrades

Automatically transform mappings in the properties table from the old format to the new one.

For the form object itself, the string value in the old format should contain the connector name. In the new format, it's a string and a couple guids. Since the guids are hardcoded for each name, this should be possible.

For field mappings, the string format is similar to forms but has additional field information. We should be able to transform with a string replace.

We should do this via database migration using epi-updatedatabase.

Fix Version/s: EPiServer.MarketingAutomationIntegration.HubSpot 4.0.0;
Jul 01, 2018
MAI-1175
  Hubspot: Data not updated if form submitted second time with same email

When a form mapped to Hubspot is submitted, it is only successful the first time. Subsequent submissions with the same email value are not successful. It works fine if the email value is changed.

Fix Version/s: EPiServer.MarketingAutomationIntegration.HubSpot 3.2.1;
Apr 22, 2018
MAI-1034
  MAI: Add support for CMS version 11.
Fix Version/s: EPiServer.MarketingAutomationIntegration.Eloqua 3.3.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.3.0; EPiServer.MarketingAutomationIntegration.Hubspot 3.2.0; EPiServer.MarketingAutomationIntegration.Marketo 3.2.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.2.0; EPiServer.MarketingAutomationIntegration.Pardot 3.2.0;
Jan 21, 2018
MAI-1027
  Performance improvements for MAI
  • Improve the performance of the connectors by fetching and caching databases and lists (wherever applicable) upon site startup.
  • Add a scheduled job that fetches data at a configured interval and refreshes cached items.
  • In the Global Settings area, add a field to set cache duration.
Fix Version/s: EPiServer.ConnectForMarketingAutomation 4.2.0; Episerver.Marketing.Automation.Forms 1.3.0; EPiServer.MarketingAutomationIntegration.Eloqua 3.2.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.2.0; EPiServer.MarketingAutomationIntegration.HubSpot 3.1.0; EPiServer.MarketingAutomationIntegration.Marketo 3.1.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.1.0; EPiServer.MarketingAutomationIntegration.Pardot 3.1.0; EPiServer.MarketingAutomationIntegration.Salesforce 3.1.0; EPiServer.MarketingAutomationIntegration.Silverpop 3.1.0;
Dec 10, 2017
MAI-971
  MAI Connectors: Crytographic error if site deployed to server with different machine key.

If credentials are saved and the site/database is deployed to a server whose machine key is different, the site throws cryptographic error and becomes unusable.

Fix Version/s: EPiServer.ConnectForMarketingAutomation 4.0.0; EPiServer.MarketingAutomationIntegration.Eloqua 3.0.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.0.0; EPiServer.MarketingAutomationIntegration.HubSpot 3.0.0; EPiServer.MarketingAutomationIntegration.Marketo 3.0.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.0.0; EPiServer.MarketingAutomationIntegration.Pardot 3.0.0; EPiServer.MarketingAutomationIntegration.Salesforce 3.0.0; EPiServer.MarketingAutomationIntegration.Silverpop 3.0.0; Episerver.Marketing.Automation.Forms 1.1.9;
Aug 13, 2017
1 2 Next