DxH architecture connects Ektron to external systems, and shares data and content with third-party applications. DxH includes these components:

• Digital Experience Hub—The core component that transfers information between Ektron and external applications through application-specific connectors.
• Inbound Connector—Transfers information between Ektron and DxH.
• HubSpot Connector—Transfers information between HubSpot and DxH.
• Marketo Connector—Transfers information between Marketo Lead Manager and DxH.
• Microsoft Dynamics® Connector—Transfers information between Microsoft Dynamics CRM and DxH.
• Salesforce® Connector—Transfers information between Salesforce and DxH.
• SharePoint® Connector—Transfers information between SharePoint and DxH.

The following figure shows the relationship among DxH components, Ektron, and external applications.

You want to let customers alert you about an issue on your website and use that information to create a Salesforce case and subsequent customer contact.

1. An Ektron administrator has previously set up:
   • an inbound DxH connection, which exchanges information between Ektron and DxH
   • a Salesforce connection, which coordinates with the Salesforce administrator to determine path and authentication information
2. The Ektron user coordinates with their Salesforce business partner to determine what data is required to create a Salesforce case.
3. The Ektron user creates a form to capture customer information concerning an issue, such as name, contact information, product name, issue type and description.
4. The Ektron user maps the form's fields to fields in Salesforce.
5. The Ektron user publishes the form to the website.
6. A customer accesses the website and submits the form reporting an issue.
7. The form goes to DxH, which uses the Salesforce Connector to route the data to Salesforce.
8. Salesforce creates a case and, if applicable business logic is in place, routes the case to a call center.

For details about the using Salesforce with DxH, see Mapping Form Data to an External Application.

You want to capture site visitor information, create a lead based on it, then display targeted content when that visitor revisits the site.

The Targeted Content widget lets you personalize your site visitors' experience by providing content that matches their interests, thereby placing your site information in the context of your users. For example, the search keywords used to find your site might determine the best offer to show a prospect. Or, site members might explicitly state their interests by adding to their user profile or filling out a survey. For information about the Targeted Content widget, see Creating and Using Widgets.

1. An Ektron administrator has previously set up:
   • DxH inbound connectionA special DxH connection type that updates Ektron content in response to content changes made in an external application.
   • Salesforce connection, coordinating with the Salesforce administrator to determine path and authentication information
2. Ektron user coordinates with a Salesforce business partner to determine data required to create a Salesforce lead.
3. Ektron user creates a form to capture required information from a customer, such as name, contact information, and product of interest.
4. Ektron user maps the form's fields to fields in Salesforce.
5. A customer accesses the website and submits the form.
6. The form goes to DxH, which uses the Salesforce Connector to route the data to Salesforce.
7. Salesforce creates a lead and, using the mapping, associates it with the visitor.
8. When the visitor returns to the site, DxH queries Salesforce for the associated lead properties.

For details about the DxH > Targeted Content connection, see Using DxH with the Targeted Content Widget.

You want to display SharePoint content on your website. The content is updated when changes are made in SharePoint.

1. An Ektron administrator has previously set up:
   • a DxH inbound connectionA special DxH connection type that updates Ektron content in response to content changes made in an external application.
   • a SharePoint connection, coordinating with the SharePoint administrator to determine path and authentication information.
2. A user places content into a SharePoint folder that is mapped to the Ektron Workarea. A copy of the content is updated in the Workarea.
3. As that content is updated in SharePoint, it is automatically updated in the Workarea.

For details on the DxH > SharePoint connection, see Importing SharePoint Content to Ektron.

DxH System Requirements

• Ektron 8.6 or higher
• DxH version 2.0
• Server—Same as Installing Ektron
• Network—By default, DxH uses port 808 to communicate between Ektron and external applications. Whichever port you use, ensure it is open on your firewall.
  • You must enable the Microsoft Windows Net.TCP Port Sharing Service (see How to: Enable the Net.TCP Port Sharing Service).
• External applications
  • SharePoint®
    • SharePoint 2010: Foundation, Standard, or Enterprise Editions
    • SharePoint 2007: Windows SharePoint Services 3.0, MOSS 2007
  • Salesforce®—Group, Professional, Enterprise, and Unlimited Editions
  • Marketo—Spark, Professional, and Enterprise Editions
  • Microsoft Dynamics® CRM—Microsoft Dynamics CRM 2011, Workgroup, Professional, Enterprise, and Service Provider Editions
  • HubSpot®—Enterprise
• You have administrator privileges or privileges to install DxH and create database

You can install DxH on the Ektron server or on its own server.

NOTE: If you previously installed DxH, you can upgrade to the current version. To upgrade to DxH version 2.0 from Ektron Version 8.7, click DxHInstaller.exe and follow the onscreen instructions.

1. Contact your Ektron account manager to obtain a link to download the Digital Experience Hub. See Also: Contact Ektron.
2. If you want to install DxH on the Ektron server, log into the Ektron server as an administrator (or as a user with privileges to create a database).
3. Download DxHInstaller.exe to the server to which you will install it.
4. Run DxHInstaller.exe.
5. Accept the license agreement and click Next. The port setup screen appears.

   Port 808 is the default value. If you want to use a different port, change it on this screen then follow Step 14.

6. The SQL Server DB Setup screen appears. In the Server field, enter the machine hosting the Microsoft SQL database. By default, the field is populated with (local). If you are using SQLExpress, use machine_name\SQLExpress.

   You can use either a domain or SQL Server account when creating the DB. For Ektron, we typically create a dedicated domain or SQL Server account for the database.

7. Enter the Username and Password for the server. For Trusted Connections, leave the fields empty.
8. Click Next. The database connection is tested. If the test is passed, the Ready to Install the Program screen appears.
9. Click Install. The Setup Status screen appears, followed by several screens indicating components being installed.

10. The finish screen appears, displaying the URL for connecting to DxH from Ektron. Save this information for later use.

    NOTE: You can access this information at any time via the Windows Start button > All Programs > Ektron > Dxh > Dxh Connection URL.

    —Image—

    

11. Click Finish.
12. Open your siteroot/web.config file and find this tag:

    <endpoint address="net.tcp://localhost:808/EktronConnector/tcp/EktronFormService" binding="netTcpBinding" 
    bindingConfiguration="ContextBusNetTcpBinding" contract="IEktronFormService" name="NetTcpBinding_IEktronFormService" />

13. Change localhost to the site domain where DxH is installed. For example, if DxH is installed to the domain myDxhService, the endpoint address would be net.tcp://myDxhService:808/ContextBus/EktronConnector/tcpEktronFormService.
14. If you changed the port in Step 5, edit the port number in the following line of web.config.
    

    <endpoint 
      address=”net.tcp://localhost:808/EktronConnector/tcpEktronFormService”
      binding=”netTcpBindding” 
      contract=”IEktronFormService” 
      name=”NetTcpBinding_IEktronFormService” />

Editing a DxH Connection

IMPORTANT: Editing a DxH connection may change the relationship between Ektron and DxH, which may interrupt data transfer between external applications and Ektron.

1. Go to Workarea > Settings > Digital Experience Hub > Connections. The View All Digital Experience Hub Connections screen appears.
2. Hover over a DxH connection and choose Edit. The Edit Connection to the Digital Experience Hub dialog appears.
   —Image—

   

3. Edit the information as required.
4. Click Test Connection. If the test fails, an error message appears. Verify that you have the correct URL and that it was entered correctly.
5. Click Update Connection.

Deleting a DxH Connection

IMPORTANT: Deleting a connection stops data transfer between Ektron and an external application.

1. Go to Workarea > Settings > Digital Experience Hub > Connections. The View All Digital Experience Hub Connections screen appears.
2. Hover over a DxH connection and choose Delete. The Delete Connection to the Digital Experience Hub dialog appears.
   —Image—

   

3. Click Confirm.

Prerequisites

• You are a member of the Ektron Administrators group or assigned a DxH Administrator role.
• The following components are installed and configured: DxH, DxH connection, and inbound connectionA special DxH connection type that updates Ektron content in response to content changes made in an external application.. See Setting Up the Digital Experience Hub.
• You have access information for external applications that will connect with Ektron via DxH. Obtain this information from the external application administrator before adding a connection.
  • Marketo
    • API path (URL)
    • Client ID
    • Encryption Key
  • Microsoft Dynamics
    • Username
    • Password
    • Fully Qualified Domain Name
    • Organization Name
  • Salesforce
    • API Key (security token)
    • Username
    • Password
  • SharePoint
    • URL
    • Domain
    • Username
    • Password
  • HubSpot
    • API Key (hapikey)

Editing a Connection to an External Application

IMPORTANT: If you rename a SharePoint Connection, the associated Workarea folder is also renamed.

1. Go to Workarea > Settings > Digital Experience Hub > Connections. The View All Digital Experience Hub Connections screen appears.
2. Hover over the connection and choose Edit from the pop-up menu. The Edit Connection dialog appears.
   —Image—

   

3. Edit the path or authentication information as required. You cannot edit the connection name.
4. Click Test Connection. If the test fails, an error message appears. Verify that you have the correct path and authentication information
   
5. Click Save Connection. The View All Digital Experience Hub connections screen appears.

Deleting a Connection to an External Application

IMPORTANT: Deleting a connection removes the relationship between the instance of the external application and DxH.This action stops all data transfer.

1. Go to Workarea > Settings > Digital Experience Hub > Connections. The View All Digital Experience Hub Connections screen appears.
2. Hover over the connection and choose Delete from the menu. A confirmation dialog appears.
3. Click Delete.

Setting Up a SharePoint 2010 Receiver

1. Run the SharePoint Receivera software module that automatically transfers updated SharePoint content to Ektron. installation file on a SharePoint server.
2. Go to the SharePoint Central Administration screen > System Settings > Manage Farm Solutions. Make sure the status of ektronsharepointreceiver.wsp is Deployed.
3. Log into your SharePoint Web application.
4. Access the Site Settings screen > Manage Site Features.
5. Click Activate to activate the EktronSharePointReceiver.
   —Image—

   

6. Place the following bindings into each SharePoint Web application's top-level web.config file (which resides within the content root folder). Insert bindings within the <system.servicemodel> section.
   

   <bindings> 
    <netTcpBinding> 
     <binding name="SharePointConnectorNetTcpBinding" 
     portSharingEnabled="true" closeTimeout="00:02:00" 
     openTimeout="00:02:00" receiveTimeout="00:10:00" 
     sendTimeout="00:02:00" maxBufferSize="2147483647" 
     maxConnections="10" maxReceivedMessageSize="2147483647"> 
     <readerQuotas maxStringContentLength="2147483647" 
       maxArrayLength="2147483647" maxBytesPerRead="2147483647" 
       maxNameTableCharCount="2147483647"/> 
     <security mode="None"> 
     </security> 
     </binding> 
    </netTcpBinding>
   </bindings>
   <client> 
     <endpoint name="SharePointAdapter_ISharePointEventReceiver" 
   address="net.tcp://localhost:9002/SharePointConnector/tcp/SharePointEventReceiver" 
   binding="netTcpBinding" 
   bindingConfiguration="SharePointConnectorNetTcpBinding" 
   contract="Ektron.DxH.SharePointConnector.Common.ISharePointEventReceiver"> 
     </endpoint>
   </client>
   

7. In the <endpoint> address property, update the text following net.tcp:// (in red above) to indicate the path and port to which DxH is installed.

Setting Up a SharePoint 2007 Receiver

1. On the SharePoint server, run the SharePoint Receivera software module that automatically transfers updated SharePoint content to Ektron. installation file.
2.  Verify the SharePoint receiver is deployed. To do this:
   1. Click Start > Administrative Tools > SharePoint 3.0 Central Administration.
   2. Log in to the Central Administration site.
   3. Under Global Configuration, select Solution Management.
   4. Check that the entry for SharePoint receiver is deployed.
3. Log into your SharePoint site.
4. Click Site Actions > Site Settings.
   —Image—

   

5. Select Site Features.

   —Image—

   

6. On the Site Features screen, click Activate to activate the EktronSharePointReceiver.
7. Open each SharePoint Web application's top-level web.config file (which resides within the content root folder).
8. Place the following bindings into that file, within the <system.servicemodel> section.
   

   <bindings> 
    <netTcpBinding> 
     <binding name="SharePointConnectorNetTcpBinding" 
       portSharingEnabled="true" closeTimeout="00:02:00" 
       openTimeout="00:02:00" receiveTimeout="00:10:00" 
       sendTimeout="00:02:00" maxBufferSize="2147483647" 
       maxConnections="10" maxReceivedMessageSize="2147483647"> 
     <readerQuotas maxStringContentLength="2147483647" 
       maxArrayLength="2147483647" maxBytesPerRead="2147483647" 
       maxNameTableCharCount="2147483647"/> 
     <security mode="None"> 
     </security> 
     </binding> 
    </netTcpBinding>
   </bindings>
   <client> 
     <endpoint name="SharePointAdapter_ISharePointEventReceiver" 
     address="net.tcp://localhost:9002/SharePointConnector/tcp/SharePointEventReceiver" 
     binding="netTcpBinding" bindingConfiguration="SharePointConnectorNetTcpBinding" 
     contract="Ektron.DxH.SharePointConnector.Common.ISharePointEventReceiver"> 
     </endpoint>
   </client>
   

9. In the <endpoint> address property, update the text following net.tcp:// (in red above) to indicate the path and port to which DxH is installed.

Deactivating a SharePoint Receiver

To suspend automatic updating of SharePoint content in Ektron:

1. Log into your SharePoint Web application.
2. Access the Site Settings screen > Manage Site Features.
3. Deactivate the Ektron SharePoint Receivera software module that automatically transfers updated SharePoint content to Ektron..

Preparing Ektron Metadata to Support SharePoint Import

NOTE: If you are not familiar with Ektron metadata, please read Working with Metadata.

While setting up the import of SharePoint files to Ektron, you may map SharePoint metadata to Ektron metadata. (In SharePoint, extra information about files is stored in columns, which are equivalent to metadata.) If you map, as SharePoint content is imported to Ektron, SharePoint metadata values are applied to corresponding Ektron metadata fields.

NOTE: To complete step 1, you must either have access SharePoint, or ask your SharePoint administrator for the information that is collected.

To prepare Ektron metadata to map to SharePoint fields:

1. Obtain the type of each SharePoint column/metadata field you want to import to Ektron. To do so,
   1. Go to the SharePoint library or list that contains the content.
   2. Choose Library Settings > Columns.
   3. Within the Columns area, find each SharePoint column/metadata field applied to the folder and its type.
   —Image—

   

   IMPORTANT: You can only choose SharePoint column types that correspond to these Ektron metadata types:
   * Byte
   * Date
   * Double
   * Float
   * Integer
   * Long
   * Multiple selections
   * Number (generic)
   * Select from a list
   * Short
   * Text
   * Yes or no
   For example, you cannot choose the SharePoint column type Person or Group, because there is no corresponding Ektron metadata type.
   

2. Go to Workarea > Settings > Configuration > Metadata Definition.
3. Click Add Metadata Definition.
4. Enter a Name for the metadata definition.
5. For Type, choose Searchable Property.

   NOTE: You can only map Searchable Property metadata types to SharePoint files.

6. In the Style field, select a type that matches the SharePoint column field type obtained in Step 1. See Also: Adding a Metadata Definition
   • The SharePoint type of Choice > Drop-Down Menu or Radio Buttons maps to the EktronSelect From a List style.
   • The SharePoint type of Choice > Checkboxes (allow multiple selections) maps to the Ektron Multiple Selections style.
   • The SharePoint type of Currency maps to the Ektron Float style.
   • The SharePoint type of Yes/no (check box)maps to the Ektron Yes or No style.
7. Repeat Steps 3 through 6 for each metadata definition you want to import.
8. Assign the metadata definitions to folders to which you will import SharePoint content. See Also: Assigning Metadata to a Folder
9. Import one SharePoint document to Ektron and verify that its metadata imports correctly. If it does not, try applying a different Style to the Ektron metadata definition.

NOTE: If you add a new metadata definition but do not see it on the DxH Map Metadata to Ektron Folder screen, reset IIS on the Ektron server.

After you verify that the SharePoint fields are properly mapped to Ektron metadata fields, proceed with the other aspects of importing SharePoint content to Ektron.

Mapping Imported SharePoint Content into Ektron

Mapping SharePoint lists, libraries, or individual files to an Ektron folder, accomplishes 2 tasks:

• Immediately starts to import selected SharePoint files, lists, and libraries.
• If the SharePoint Receivera software module that automatically transfers updated SharePoint content to Ektron. is activated, all updates to and deletions of SharePoint files trigger an automatic update/deletion to the version stored in Ektron. Also, new files added to SharePoint lists and libraries are automatically copied to the mapped Ektron folder.

To set up the SharePoint-to-Ektron mapping:

1. On the Ektron Workarea's Content tab, navigate to the destination folder.
2. Choose New > DxH Content > Add SharePoint Content. The Select SharePoint Connection screen appears.
3. Choose a SharePoint Connection, and click Start. The Select SharePoint Content screen appears.
4. At the What SharePoint® content would you like to add from "My SP" Connection? field, choose one of these options.
   • All current and future items from SharePoint® Lists or Libraries—When you select a list or library, all files within it and its subfolders are imported. And, any files added to or deleted from or updated within that list or library in the future are updated in the selected Ektron folder.

     NOTE: Deletions depend on your choice in the next field.
     

   • Items from SharePoint® Lists or Libraries—You choose individual files from several lists and libraries. If the files are updated or deleted in the future, they will be updated in the selectedEktron folder.

     NOTE: Deletions depend on your choice in the next field.

5. At the In what language should this content be imported? field, select a language for the imported content. The drop-down shows all enabled languages. See Also: Determining Which Languages are Available

   NOTE: This field only appears if more than one language is enabled in the Ektron Workarea.
   

6. At the If the content you select is deleted from SharePoint® in the future, what should happen to the Ektron copy of that content? field, choose one of these options.
   • Do NOT delete it from Ektron—If the file is deleted from SharePoint, leave the Ektron copy as is.

   • Delete it from Ektron—If the file is deleted from SharePoint, delete it from Ektron.

7. The next screen depends on your response to the What SharePoint® content would you like to add from "My SP" Connection? field. If you chose
   • All current and future items from SharePoint® Lists or Libraries—The following screen appears. Choose SharePoint lists/libraries that you want to import.
     —Image—

     

   • Items from SharePoint® Lists or Libraries—Choose files from several lists and libraries. When you click a list or library, its items appear in the top right grid. As you check items to import, they appear in the lower grid.
     
     —Image—

     

8. The Map Metadata to Ektron Folder screen appears. For background information on this screen, see Preparing Ektron Metadata to Support SharePoint Import.
   —Image—

   

   You may map as many Ektron metadata fields to SharePoint metadata fields as you wish.

   Required Ektron fields have an asterisk (*). If you do not map required metadata fields, you may proceed but when the content is imported to Ektron, its status is Checked-In. The content can only be published after required metadata values are entered.

9. Click Next then Done. It takes a while to import the SharePoint files. The length of time depends on the number and size of the files.

Updating SharePoint Content Manually

Typically, the SharePoint Receivera software module that automatically transfers updated SharePoint content to Ektron. handles this task for you. You only need the manual import if the SharePoint receiver is not installed or is inactive. See Also: Setting Up a SharePoint Receiver

Prerequisite

You have 1 of the following Ektron designations:

• Administrators group member
• DxH Connection User RoleA limited or specific administrator privilege that you can assign to users who do not require full administrator privileges.
• Folder-Admin role
• Edit permissionPermissions determine which actions users and user group members can perform on content, library items, and content folders. You can set permissions for a folder and content.s for the folder containing SharePoint content

Use the manual update feature to transfer a file to Ektron immediately. You also can manually transfer an updated image file that is embedded within SharePoint content. Without a manual update, that image only transfers to Ektron when the related SharePoint content is updated.

1. In SharePoint, edit either the SharePoint document/file or its properties.
2. Navigate to the folder that contains the content you want to update.
3. Click the arrow to the right of the content title.
4. Click Update DxH Content.
   —Image—

   

NOTE: When a user imports a SharePoint content item to an Ektron folder that already contains the item, that action also updates the Ektron content.

Creating a Mapped Form

1. Obtain the following from the external application's administrator:
   • Form/record name

     NOTE: Only these forms are supported:
     * Marketo Lead Management—Lead
     * Salesforce—Lead, Contact, Account
     * Microsoft Dynamics CRM—Lead, Contact, Account
     * HubSpot—Contacts
     

   • Form fields that you will map to an Ektron form.
   • Data type for each form field. Only these types are available in Ektron, so the external application field's data types must match one of them.
     • Checkbox—User’s response is checked or unchecked (boolean)
     • Choices—Several choices available. User selects any number of choices
     • Calendar—A date
     • Text—Free text

     IMPORTANT: Coordination is critical when mapping form fields to external applications. Before creating a form, contact your business partner for the application and determine which fields are required to complete the desired action.

2. Create a new HTML form. See Also: Creating a Form
3. On the second screen of the Create Form wizard, check DxH Mapping.
   —Image—

   

4. Complete the steps for creating the form. When inserting form fields, refer to information collected in Step 1.
5. Publish the form.
6. Edit the form and, from its toolbar, click Map to DxH. The Map Form to DxH screen appears.
7. Enter a name for this mapping. It must be unique and easy to recognize.
8. Select the connection to the external application. You created this in Setting Up a Connection to an External Application.
9. From the Object Type drop-down, select the external form with which to map this Ektron form. The following forms are supported:
   • Marketo Lead Management—Lead
   • Salesforce—Lead, Contact, Account
   • Microsoft Dynamics CRM—Lead, Contact, Account
   • HubSpot—Contact

   NOTE: You obtained the form name in Step 1.

10. Click Next. The Map Required Form Fields screen appears. All required external fields appear in the left column. Use the drop-down in the right column to map one Ektron form field to each required field.

    IMPORTANT: The external application field's data type must match the Ektron form field .

    —Image—

    

11. When the Map Optional Form Fields screen appears, follow instructions in Step 10 to map Ektron form fields to optional external fields.
12. Click Publish. The Form Mapping Completed screen appears.
13. Click Test Form Mapping. A new form appears, showing fields that you mapped.
14. Enter sample data into each field and click Test Mapping. You are notified if the sample data is valid.
15. Click OK.

IMPORTANT: The Form Mapping Complete dialog indicates that mapping between form fields and the external application object has been established, but does not indicate that the mapping is valid. You should perform end-to-end system testing to ensure that form fields pass successfully between systems.

When a site visitor submits a mapped form, the external application creates a record (Lead, Account, or Contact). You may edit the record in the external application.

Mapping an Existing Form to an External Application

1. Go to Workarea > Content > {the folder that contains the form}.
2. Click the form. The View Form screen appears.
3. Click Map to DxH. The Map Form to the Digital Experience Hub dialog appears.
4. Enter a name for this mapping. It must be unique and easy to recognize.
5. Select the connection to the external application. You created this in Setting Up a Connection to an External Application.
6. From the Object Type drop-down, select the external form with which to map this Ektron form. The following forms are supported:
   • Marketo Lead Management—Lead
   • Salesforce—Lead, Contact, Account
   • Microsoft Dynamics CRM—Lead, Contact, Account
   • HubSpot—Contact

   NOTE: You obtained the form name in Step 1.

7. Click Next. The Map Required Form Fields screen appears. All required external fields appear in the left column. Use the drop-down in the right column to map one Ektron form field to each required field.

   IMPORTANT: The external application field's data type must match the Ektron form field .

   —Image—

   

8. When the Map Optional Form Fields screen appears, follow instructions in Step 7 to map Ektron form fields to optional external fields.
9. Click Publish. The Form Mapping Completed screen appears.
10. Click Test Form Mapping. A new form appears, showing fields that you mapped.
11. Enter sample data into each field and click Test Mapping. You are notified if the sample data is valid.
12. Click OK.

Editing a Form that is Mapped to an External Application

After a form is mapped to an external application, you can edit the map properties.

1. Go to Workarea > Content > {the folder that contains the form}.
2. Click the form. The View Form screen appears.
3. Click Edit DxH Mapping. The Map Form to the Digital Experience Hub dialog appears.
4. Edit the form properties as required.
5. Click Publish. The Form Mapping Completed dialog box appears.
6. Click Close.

Deleting a Mapped Form

If you try to delete a form mapped to an external application, a dialog notifies you that by deleting the form, you are also deleting the mapping. Click Delete to delete the form and mapping.

Using DxH with the Targeted Content Widget

You can use data collected through Ektron forms and stored in an external application in a Targeted Content widget. When a user submits a mapped form, the external application connector writes a user ID for that login back to Ektron. This enables the delivery of targeted content based on the user's identity.

You can use the Targeted Content widget to personalize a Web page by displaying content based on information from a user-completed form. For example, if the Salesforce lead's industry is healthcare, the page may display content of interest to healthcare professionals. See Also: Creating and Using Widgets

To use DxH with a Targeted Content widget:

1. Determine Targeted Content widget criteria from the external application forms and fields in the siteroot/dxhTargetingRules.config file. The following sample shows a portion of this file (which are in the file by default).
   Sample dxhTargetingRules.config

   <dxhRules>
     <Adapter name="Salesforce">
       <AdapterObject name="Lead">
         <add name="Company Name" value="Company"/>
         <add name="Industry" value="Industry"/>
         <add name="Number of Employees" value="NumberOfEmployees"/>
         <add name="Revenue" value="AnnualRevenue"/>
         <add name="Products Owned" value="Products Owned"/>
         <add name="Product Interest" value="ProductInterest"/>
         <add name="Score" value="Rating"/>
       </AdapterObject> 
     </Adapter>

   Tag Descriptions

   • dxhRules—The file's root tag.
   • Adapter—The adapter for which to display object rules, such as Salesforce or MSDynamics. It is not the connection name (for example, marketingSF).
   • AdapterObject—The system name of the object within the specified adapter. For example, to enter a Salesforce lead, insert the system name Lead (case-sensitive).
   • add—The field. The name attribute contains text that the end user sees (as shown in the following image). The value attribute contains the system name of the field.
     —Image—

     

   NOTE: The field's datatype is recognized and automatically surfaced into the correct rule type; numeric rule for an integer or decimal, string rule for a string, a multi-select rule for a pick list, and so on.

2. Access either a Targeted Content widget or a Targeted Content configuration. See Also: Creating and Using Widgets; Reusing Targeted Content Widgets on Web Pages
3. Click the Or+ button to add a criterion for the widget.
4. Select an adapter and field. For example, Salesforce Lead > Industry.
5. Enter additional fields as you would in any Targeted Content widget or configuration.
6. Save the widget and test it.