This guide will help you get up and running with the Salesforce plugin from Data8. We will cover the initial steps including installation of the plugin itself, and then explain the configuration settings available within the plugin. Once these are set up to suit your needs, the guide will discuss how to configure your salesforce environment to make use of the custom components and integrations available.
Contents of this guide:
- Install the Data8 Salesforce plugin: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t3w000001Z0zW. For Sandbox installation, use `test.salesforce.com` instead of `login.salesforce.com`.
- Sign into your organisation and click the ‘Install’ button.
- Agree to allowing requests to the `webservices.data-8` domain as this is necessary for our validation API’s to work.
- Once you see the installation complete screen, click the done button.
The settings page contains all of the configuration options for Data8 Address Capture and Validation. It can be accessed by searching 'Data8' or 'Settings' in the app launcher quick search bar.
There are many options available on this page that control how the Data8 services work. The table below explains each option and should help getting the plugin set up to suit your needs.
|Data8 Server-Side API Key||An API Key generated from the Data8 Dashboard, with at least one IP address added to the list of 'Allowed IP's' and no domains added.|
|Data8 Client-Side API Key||An API Key generated from the Data8 Dashboard, with at least one domain added to the list of 'Allowed Domains'. Only required for PredictiveAddress.|
|Load Record On Save||This option determines whether the saved record is displayed after saving, or if a new, blank form is created. Only used with record form override implementation.|
|Use PredictiveAddress||Enable PredictiveAddress (Address Autocomplete Tool) on address fields.|
|PredictiveAddress Mappings||Configure mappings to tell our service what address fields to attach autocompletion to and where to store the selected address. Custom objects and fields are supported.|
|Country Limiting||Restrict the countries in which PredictiveAddress searching can be performed. Can be limited by allowed countries or barred countries.|
|Max Line Length||The maximum number of characters per line in the formatted address. Defaults to 255.|
|Street Line Count||The number of lines to split the street data in the formatted address over.|
|Unwanted Punctuation||A string containing any characters that should be excluded from the formatted address.|
|Include Not Yet Built||Includes addresses from the Not Yet Built database in the results (requires additional licensing).|
|Include Multiple Residencies||Includes addresses from the Multiple Residency database in the results (requires additional licensing).|
|Use Geocoding||Returns the latitude and longitude of the returned address.|
|Include On Record Forms||Whether or not to display the PredictiveAddress service on the create and edit forms of records (when using the record form override implementation).|
|Minimal Company Information||Limit the amount of data which the Company Information service displays.|
|Create Contact For Directors||Create contacts for each director when using our company lookup tool.|
|Use TPS||Check whether entered telephone numbers are registered with the TPS.|
|Use CTPS||Check whether a telephone number is registered with the CTPS|
|TPS/CTPS Mappings||Select which fields TPS and CTPS checks should be performed on per object. Create a custom picklist field for the TPS result, which uses the TPS Status picklist set. Optionally create a Date field to store the Date/Time of last TPS check performed on the record.|
|Use Account TPS Triggers||Option to use legacy triggers instead of lightning component or record form override. Hard-coded to check default telephone fields on Account object. Mappings will still need to be configured accordingly to use the TPS Status display.|
|Use Contact TPS Triggers||Option to use legacy triggers instead of lightning component or record form override. Hard-coded to check default telephone fields on Contact object. Mappings will still need to be configured accordingly to use the TPS Status display.|
|Use Lead TPS Triggers
||Option to use legacy triggers instead of lightning component or record form override. Hard-coded to check default telephone fields on Lead object. Mappings will still need to be configured accordingly to use the TPS Status display.|
|Use Bank Account Validation||Determine if a sort code and bank account number is valid and retrieve additional information about the bank.|
|Use Bank Address Lookup||Obtain the address of the bank after validating the entered details.|
|Bank Validation Mappings||Select which fields bank validation should attach to. Create custom Text fields are created for Sort Code and Account Number. Optionally, create custom Text fields for Bank Name, Bank Branch Name, Bank Address, IBAN and BIC Code as these can be populated with data returned from the bank validation check.|
|Use Email Validation||Checks an email address for validity at the requested level.|
|Email Validation Level||
The level of validation to apply to email fields.
Syntax. The supplied email is checked to ensure that it meets the standard email address format. This is the quickest option and would reject such incorrect email addresses as "noone@nowhere" and "N/A", but would accept incorrect email addresses that are correctly formed but that do not include a valid domain name such as "email@example.com"
MX. The supplied email is checked to ensure that the domain name (the part to the right of the @ sign) exists and is set up to receive email.
It does not verify that the part of the email address to the left of the @ sign exists.
Server. In addition to the MX level checks, validates that at least one of the mail servers advertised for the domain is actually live.
Address. In addition to the Server level checks, validates that the mail server accepts mail for the full email address.
|Use Telephone Formatting||Converts entered telephone numbers to their standard format.|
|Options||Options for Telephone Formatting service such as "DefaultCountryCode" and "DefaultFormatType"|
|Use International Telephone Validation||Checks entered telephone numbers for validity.|
|Use Landline Validation||
If set to true, then the service will use Landline Validation on any number it recognises as a UK landline number and International Telephone Validation on all other numbers. Requires additional Landline Validation credits.
|Use Mobile Validation||If set to true, then the service will use Mobile Validation on any number it recognises as a mobile number and International Telephone Validation on all other numbers. Requires additional Mobile Validation credits.|
|Default Country Code||If a number is supplied as a national number, the default country code is used to identify which country the number is located in. The default country code can be supplied as any of:
international telephone dialling code (e.g. 44)
|Use Unusable Name Validation||Checks to see if entered names are usable or if they is Salacious, Random or Blank.|
For non-admin users to make use of Data8's services, they will need the `Data8 User` permission. To set this, go to Setup > Permission Sets > Data8 User > Manage Assignments > Add Assignments > select all users to apply permission to > Assign.
The Next Steps:
The next section of this guide will demonstrate how to set up the main (recommended) integrations for our services. All integrations will also work in Salesforce classic, other than the Lightning Components.
The recommended implementation for this section of the guide is the Record Form Override method. This gives you access to our email validation, international telephone validation, name validation, bank account validation, PredictiveAddress, TPS checking, and telephone formatting services all in one place, when creating or editing records. This method replaces the standard pop-out modal form used for editing and creating records with a full-width visualforce page and makes use of your object's page layout ensuring compatibility with custom fields. You will need credits on your Data8 account for each service to be able to use them. Speak to your account manager if you wish to get set up with some credits for a new service.
If you are using Lightning in your Salesforce environment, the Lightning Component methods may also be a useful integration, adding bank account validation, TPS checking, PredictiveAddress and Business Insights to your lightning record forms for easy TPS checking, bank validation and quick and accurate address entry. This method supports custom objects and custom fields (excluding Business Insights which is for accounts and leads only. Contact us if you wish to use this service on another object). See our Bank Validation Configuration, TPS Configuration, PredictiveAddress Configuration and Business Insights Configuration guides accordingly.
Our Business Insights (company information) service, which adds the ability to find and link company data to an account record, such as credit rating, recommended credit limit, company summary, addresses, shareholders, group structure and much more, can be implemented through a Lightning Component or Visualforce page and custom action button.
Once you have configured your Salesforce environment to make use of the integrations you wish to use, read our User Guide for information on how to use our services.
|Bank Account Validation||Record Form Override, Lightning Component|
|Business Insights (Company Information)||Business Insights, Lightning Component|
|Email Validation||Record Form Override|
|Name Validation||Record Form Override|
|PredictiveAddress||Record Form Override, Lightning Component, Custom Button (VF Page)|
|Telephone Formatting||Record Form Override|
|Telephone Validation||Record Form Override|
|TPS Checking||Record Form Override, Lightning Component, Triggers|