From Bright Pattern Documentation
< 3.18:Sfdc-integration-guide
Revision as of 18:54, 5 March 2018 by Tracy (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Importing Calling Lists and Exporting Campaign Results

You can import calling lists for your outbound campaigns directly from Salesforce.com (SFDC) and set up automated periodic updates of such lists to include changes made to the corresponding data in SFDC. You can also automatically create SFDC records based on campaign results.

In order to enable import of calling lists and export of campaign results, the integration steps of section Enabling Access to SFDC Data from Scenarios must be completed first.


How to Import List Data from SFDC

Step 1: Create a list.

  • In the Contact Center Administrator application, select Lists, and click the Import list button. This will start the List Import Wizard.
  • In the first wizard screen (List Type), select Create a list from Salesforce.com SOQL query.
  • Click Next.


Sfdc-integration-guide-image25.PNG


Step 2: Name your list.

  • Assign a unique Name to your list.
  • Select the Saleforce.com integration account, and specify the query for selecting Saleforce.com records for this calling list. The query must be written in the Salesforce Object Query Language (SOQL). Note that the selected records must contain object identifiers and must have at least one phone number field.
  • Click Next.


Sfdc-integration-guide-image26.PNG


Step 3: Review and Edit list fields if needed.

  • Edit the list fields as may be necessary. For more information, see section Lists of the Contact Center Administration Guide. Note that SFDC object identifiers will be used as keys for list record identification; therefore, field ID will be automatically marked as a required field.
  • Click Next.


Sfdc-integration-guide-image27.PNG


Step 4: Confirm import results.

  • Review the results of import, and click Ok.
  • In the List Properties view, enable periodic updates of this list. (Note that for lists of Salesforce.com type, new records matching the original SOQL query will be added to the list during each update, while any records that may have been removed from Salesforce will be disabled in the list. If there are campaign results available for such disabled records, they will be preserved.)
  • Click Apply.


Note: There is a 30-second timeout on the Bright Pattern side to begin receiving data from SFDC after the SOQL query is submitted. This timeout applies to both the initial list import and subsequent periodic updates.

How to Export Campaign Results to SFDC

Step 1: Select a campaign.

  • In the Services and Campaigns view of the Contact Center Administrator application, select a campaign.
  • Click the add link under Periodic Salesforce.com Export Jobs.
  • Note that there is no dependency between data export and import. Export to SFDC can be configured for any campaign regardless of the source of the data.


Step 2: Specify export job parameters and type of object to be created.

  • Define the general parameters of the export job.
  • Select the Salesforce.com integration account.
  • Specify the type of Salesforce.com object that will be created using the results of this campaign.


Sfdc-integration-guide-image28.PNG


Step 3.

  • Click the Map fields button and map properties of the specified Salesforce.com object to the corresponding campaign result fields.
  • In the dialog that appears, for each object property that will be defined using the campaign data, click the $() link.
  • Select the corresponding field of the campaign results, and, if necessary, edit it in the Value to set field.
  • Note that object fields of type ID are generated automatically by SFDC and cannot be modified.


Sfdc-integration-guide-image29.PNG


Step 4: Test the results of the export.

  • Click the Test by creating object button.
  • Check that an object of the specified type is created in SFDC with the mapped properties filled with test data.



< Previous | Next >
< Previous | Next >