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. Troubleshooting
  14. Appendix A: Custom Settings
  15. Appendix B: Glossary

Status of Records in the EventQueue Table

Status of Records in the EventQueue Table

The DaaS job creates a transaction entry for the records processed in the EventQueue table and sets the status to
Pending
. The external adapter changes the status based on the response from the address, email address, and phone number verification service.
The DaaS job receives the response from the verification service and updates the following transaction status:
Pending
Indicates that the DaaS job has not yet verified the records.
Failed
Indicates that the DaaS job has failed to verify the records. The job updates the status for the failed records as
Failed
in the EventQueue table.
Completed
Indicates that the DaaS job has successfully verified the records. The job deletes all records that have been verified successfully from the EventQueue table. The DaaS job also creates a chatter feed for all successfully validated records.
Uncommitted
Indicates that the record belongs to any operation that is not yet saved in the database.
Not Verified
Indicates that the subject fields of the transaction records have not been verified.
Valid
Indicates that the subject fields of the transaction records have been verified and they are valid.
Invalid
Indicates that the subject fields of the transaction records have been verified but they are not valid.
Undecided
Indicates that the subject fields of the transaction records have been verified but the validity is uncertain.

0 COMMENTS

We’d like to hear from you!