Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Version Info: This topic applies to Episerver.ConnectForMarketingAutomation 4.0.0 and lower. For later versions, see Sample Connector - IMarketingConnector.
This class is the main interface that the Marketing Automation Interface (MAI) plugin uses to load the connector. During the intitialize process of MAI the Service locator is used to load the connector.
Note: Only one connector can exist in the solution or be installed with the MAI framework.
System.Object
EPiServer.MarketingAutomationIntegration.Core.ProviderBase
DemoConnector.Services.Provider
public class Provider : ProviderBase
Initializes a new instance of the Provider class.
public Provider()
The name of the connector.
public override string Name { get; }
The settings for the connector.
public override IProviderSettings Settings { get; }
You can attach an external URL, the URL of the configuration page, or another URL of a page of your choosing to the main connector button at the top of the configuration screen.
public override string GetDashboardUrl()
This method is called by the MAI framework at startup, which you can use to add services to the default EPiServer IoC container.
public override void Init(
ServiceConfigurationContext serviceConfigurationContext
)
Called periodically by the MAI framework to verify that the connector is ready to use.
public override bool IsReady()
This function receives the connector data that is collected from the user. Read it in as XML and process it. This loops over the XML tags and parses out data for each one for processing. This code is executed when you click Submit on a form.
(Inherited from ProviderBase.)
public virtual void ProcessXFormData(
Object sender,
XFormDataEventArgs e
)
Last updated: Dec 10, 2015