Release notes for Episerver updates

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

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.

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.

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.

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.

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.

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

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.