Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Protection of Pending Records

Protection of Pending Records

You can protect pending records from updates that are not part of the same process. The Interaction ID controls this setting.
When base object tables or cross-reference tables include Interaction IDs, you can not use the tools in the Hub Console to change the state of a base object record or cross-reference record from PENDING to ACTIVE. When cross-reference records include an Interaction ID, the Interaction ID protects a pending cross-reference record from updates that are not part of the same process as the original cross-reference record. Use one of the state management SIF API requests, instead.
The Interaction ID can be specified through any API. However, it cannot be specified when performing batch processing. For example, records that are protected by an Interaction ID cannot be updated by the Load batch process.
The following table contains an example showing the effect of the Interaction ID field during the match process on existing and incoming records. In the example, the interaction_ID field has the following values: Version A , Version B, and null.
Incoming Record's Interaction ID
Existing Record's Interaction ID
 
Version A
Version B
Null
Version A
OK
Error
OK
Version B
Error
OK
OK
Null
Error
Error
OK

0 COMMENTS

We’d like to hear from you!