Area |
ID |
Type |
Description |
Released |
|
MAI-2093
|
|
Salesforce connector: Access token not updated in cache after re-authenticating, when session ID expires.
Fixed an issue that did not update a token in the cache when the session ID expired and used an expired token to retry authentication.
EPiServer.MarketingAutomationIntegration.Salesforce 4.3.2;
|
Mar 14, 2023
|
|
MAI-2018
|
|
Salesforce connector does not allow certain special characters (like "&") in username and password.
Fixed an issue where the Salesforce connector failed to authenticate when the ampersand ( & ) and plus ( + ) special characters were included in username and password.
EPiServer.MarketingAutomationIntegration.Salesforce 4.3.1;
|
Dec 20, 2022
|
|
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.
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;
|
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;
|
Jul 20, 2021
|
|
MAI-1827
|
|
Salesforce: When using SOAP API, failed to create leads after a session expired.
When you used SOAP API option in the settings, form submissions failed to create leads after the session expired, and generated the following error:
System.Web.Services.Protocols.SoapException: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash
EPiServer.MarketingAutomationIntegration.Salesforce 4.2.1;
|
Jun 21, 2020
|
|
MAI-1511
|
|
Salesforce: 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.
EPiServer.MarketingAutomationIntegration.Salesforce 4.1.0;
|
Dec 09, 2018
|
|
MAI-1474
|
|
Salesforce: Incorrect endpoint used to connect to Sandbox instance.
When sandbox option is chosen in the connector settings, it is incorrectly attempting to connect to the production endpoint, which throws the following error:
Error in Authentication of CredentialsINVALID_LOGIN: Invalid username, password, security token; or user locked out.
EPiServer.MarketingAutomationIntegration.Salesforce 4.0.2;
|
Oct 08, 2018
|
|
MAI-1310
|
|
Salesforce: Object reference error when fetching connector data on site initialization and scheduled job
Salesforce stores the login result object in a request variable. The process of fetching the data in the initialization module and scheduled job occurs in a parallel loop.
If the request for Salesforce data happens in a thread different from the originating one, the HttpContext is null. This results in a null reference exception.
EPiServer.MarketingAutomationIntegration.Salesforce 4.0.1;
|
Jul 22, 2018
|
|
MAI-1002
|
|
Salesforce: New (duplicate) contact created when same visitor re-submits form
When a visitor submits a form mapped to Salesforce, a new contact is created in Salesforce. But when the same visitor re-submits the form (without clearing cookies), it creates a new contact instead of updating the existing one.
EPiServer.MarketingAutomationIntegration.Salesforce 3.0.1;
|
Nov 19, 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.
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
|