Table of Contents

Search

  1. Preface
  2. Introduction to Services Integration Framework
  3. Setting Up the SIF SDK
  4. Request and Response Objects
  5. Transactions and Exception Handling
  6. ORS-Specific SIF API
  7. Asynchronous SIF Requests
  8. ORS-Specific JMS Event Messages
  9. Using Security Access Manager
  10. Using Dynamic Data Masking
  11. SIF API Reference
  12. Troubleshooting
  13. Appendix A: Identifiers
  14. Appendix B: Frequently Asked Questions

Services Integration Framework Guide

Services Integration Framework Guide

Use Cases

Use Cases

These are the common scenarios for using the cleanse request:
  • Data cleansing for external applications
    — An external application can use the cleanse request independently of the Informatica MDM Hub master record functionality. External applications can invoke cleanse to interface with data quality facilities provided by Informatica to process input data.
  • Address verification for external applications
    — Informatica MDM Hub provides the functionality to validate and standardize addresses. These facilities can be used by external applications to improve the quality of the address data that is entered into them.
  • Cleanse used in combination with put
    — The most common use of the cleanse request is to cleanse an individual field before the record is passed to the put request.
  • Cleanse used in combination with match
    — The match request provides access to the matching rules and allows you to search Informatica MDM Hub for records that contain values that are similar, but not necessarily identical to the search criteria. To improve the quality of matches returned, you can cleanse the search criteria before passing them to the match request.

0 COMMENTS

We’d like to hear from you!