Salesforce.com CRM
Overview
The following channel-specific fields are shown for Salesforce.com CRM channels:
Web service address
This mandatory text field accepts a maximum of 1000 characters. It defaults to the following value: https://login.salesforce.com/services/Soap/u/52.0/. It allows for specification of the web service address to be used to connect to Salesforce CRM.
Note that changes to the default value can have an impact on the accessibility of Salesforce data and resources.
Service username
A mandatory field, which may be a maximum length of 100 characters.
Service password
A mandatory field, which may be a maximum length of 100 characters.
Security token
A mandatory field, which may be a maximum length of 100 characters.
Allow update
By checking this checkbox, you can define that the channel will support the automatic synchronization of data updates to and from Salesforce.com. By default the checkbox is unchecked. Checking it makes the Update behavior dropdown available.
Update behavior
This dropdown is available when Allow update is checked. It exposes the following values:
Sync from Salesforce to RPI Data Warehouse (default)
Sync from RPI Data Warehouse to Salesforce
It allows you define the update behavior for the initial synchronization of lead or contact records between RPI and Salesforce.
Data to synchronize
This dropdown allows you to define the type of data the Salesforce channel will be used to manage. It exposes the following values:
Leads (the default)
Contacts
Accounts
On changing the value, if the channel has an existing set of Field parameters defined, an “Are You Sure?” dialog advises that “Changing the data to synchronize option causes the existing data field mappings to reset”, and checks that you wish to proceed. If you do, the existing Field parameter settings will be lost.
Table name
This mandatory field, with a maximum length of 50 characters, allows you to define the name of the table into which Salesforce.com data will be imported.
Field parameters
This grid facilitates the mapping of Salesforce.com fields to RPI attributes. Selecting the Load data fields toolbar button loads the available list of field parameters from Salesforce.com. If Field parameters have already been defined, an “Are You Sure?” dialog advises “Reloading data fields from Salesforce will cause your existing data field mapping to be reset” and asks you whether you wish to continue. If you elect to proceed, RPI retrieves from Salesforce a list of updatable, not system based, non-referenced data fields. An advisory message is shown if the list of fields was not able to be populated.
The following data fields warrant special mention:
LeadID: used as a lookup key when Data to synchronize is set to Leads and does not support write-back of data if Allow updates is checked, being system-generated by Salesforce (unlike other field parameters).
ContactID: used as a lookup key when Data to synchronize is set to Contacts and does not support write-back of data if Allow updates is checked, being system-generated by Salesforce (unlike other field parameters).
MobilePhone: setting this field parameter facilitates population of the Phone field at Saleforce.com’s Activity History (if configured at the Salesforce user interface).
Email: setting this field parameter facilitates population of the Email field at Saleforce.com’s Activity History (if configured at the Salesforce user interface).
Note that the Status (optional) and LeadSource fields are included in the list only to facilitate write-back of these data if Allow updates is checked; at Salesforce.com offer activity execution, the values of lead status and source are always provided by the Salesforce.com offer.
For each field parameter, the following are displayed:
Lookup key: a checkbox, unchecked by default. Lookup key is available when a field parameter is mapped to an Attribute. When checked, the field is included as a lookup key at execution of a Salesforce offer in an interaction.
Name: read only; the name of the Salesforce.com data field to which an RPI attribute is to be mapped.
Attribute: you can browse for an attribute, or you can populate using drag and drop. Once an attribute has been selected, you can invoke View Information and Clear. You can only map a given attribute once, and you can only map database column attributes (although not primary key columns). You cannot map an attribute from an auxiliary database. Mandatory attribute provision is contingent on the channel’s Salesforce data to sync property:
If set to “Leads”, the following data fields must be mapped to RPI attributes: LastName, Company and Status.
If set to “Contacts”, the following data field must be mapped to an RPI attribute: LastName.
If set to “Accounts”, the following data field must be mapped to an RPI attribute: Account Name.
In addition to the required fields mentioned above, “mandatory” or “optional” behavior of the fields are also sourced from Salesforce.com.
Data Type: read only.
Description: read only. Sourced from Salesforce’s Help Text property.
A channel’s Field parameters must be defined prior to its being saved.
Advanced tab
The following property is exposed at the Advanced tab:
Enable trace: if checked, API requests and responses will be logged at offer execution using the channel.
When the property is checked, a message displays that says “Enabling this option can impact performance and potentially persist PII data within the trace data”.