| Area |
ID |
Type |
Description |
Released |
|
MAI-1857
|
|
Marketo: Add method to schedule campaigns in the REST Service API.
Add method to schedule campaigns in the REST Service API.
EPiServer.MarketingAutomationIntegration.Marketo 4.5.0;
|
Dec 29, 2020
|
|
|
MAI-1664
|
|
Marketo: Add an option to specify workspaces from where to fetch lists from.
On the Admin Configuration screen, provide an optional text field to specify workspace names. If any workspace is specified, lists are fetched from that workspace only.
Multiple workspaces can also be given, separated by commas.
EPiServer.MarketingAutomationIntegration.Marketo 4.4.0;
|
Jun 16, 2019
|
|
|
MAI-1622
|
|
Marketo: Choose behavior of multiple form submissions in same session
Currently, multiple form submissions in the same session update the lead created on the first submission. Provide an option to create a new lead on every submission, similar to the Salesforce connector.
EPiServer.MarketingAutomationIntegration.Marketo 4.3.0;
|
Apr 07, 2019
|
|
|
MAI-1595
|
|
Marketo: Add API method to determine membership of a lead in a list
Add API methods in the service and connector to determine the membership of a lead in a list.
bool IsMemberOfList(long leadId, long listId)
EPiServer.MarketingAutomationIntegration.Marketo 4.2.0;
|
Mar 03, 2019
|
|
|
MAI-1371
|
|
Marketo: Update settings UI to allow creation of multiple instances.
EPiServer.MarketingAutomationIntegration.Marketo 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
|
Dec 09, 2018
|
|
|
MAI-1530
|
|
Marketo: Form field mapping for custom fields lost when upgrading from 3.x to 4.x.
Form field mapping for custom fields lost when upgrading from 3.x to 4.x.
EPiServer.MarketingAutomationIntegration.Marketo 4.0.4;
|
Nov 06, 2018
|
|
|
MAI-1493
|
|
Marketo: Error while fetching lead if large number of fields
While attempting to fetch a lead with a large number of fields, the Marketo connector results in an error.
"System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine".
EPiServer.MarketingAutomationIntegration.Marketo 4.0.3;
|
Oct 21, 2018
|
|
|
MAI-1465
|
|
Marketo: 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.Marketo 4.0.2;
|
Oct 07, 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.
EPiServer.MarketingAutomationIntegration.Silverpop 4.0.2; EPiServer.MarketingAutomationIntegration.Marketo 4.0.1;
|
Sep 02, 2018
|
|
|
MAI-1128
|
|
Marketo Connector for MAI 5.0.0 framework
The Marketo connector was updated to use the MAI 5.0.0 packages framework.
EPiServer.MarketingAutomationIntegration.Marketo 4.0.0;
|
Aug 19, 2018
|
