Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Cloud MDM - Customer 360 for Salesforce
  3. Configuring the Data Cleansing Settings
  4. Managing Batch Jobs
  5. Verifying Addresses, Email Addresses, and Phone Numbers
  6. Synchronizing Salesforce Records with CC360
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Cloud MDM - Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Custom Settings
  14. Glossary

Address, Email Address, and Phone Number Verification Process

You can run the DaaS job to verify the contact information. The DaaS job uses address verification service to verify address, email address verification service to verify email address, and phone number validation service to validate phone number. The DaaS job also uses service mappings to map the fields between the Salesforce fields and the DaaS fields.
Use the template for the DaaS job to schedule the job, select the objects, and the records that you want to verify. You can create multiple instances of the job to verify records based on your requirements or specifications. Every record that the DaaS job processes is stored as a transaction entry in the EventQueue table.
In the Lightning Experience, for email address and phone number fields, transaction entry is created only after you click the
Click to Verify
button. In Salesforce Classic, transaction entries for all the fields are created as you enter the values.
The following image shows how the DaaS job verifies the contact information:
The image shows the contact data verification process. You can run the data as a service batch job to verify contact data of standard and non-standard objects in your Salesforce organization. The DaaS batch job uses the DaaS mappings, address verification service settings, email verification service settings, and phone validation service settings. Every record that the DaaS job processes is stored as an entry in the EventQueue table.

0 COMMENTS

We’d like to hear from you!