Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Promote Jobs

Promote Jobs

For state-enabled objects, the Promote job reads the PROMOTE_IND column from an XREF table and changes the system state to ACTIVE for all rows where the column’s value is 1.
Informatica MDM Hub resets PROMOTE_IND after the Promote job has run.
The PROMOTE_IND column on a record is not changed to 0 during the promote batch process if the record is not promoted.
Here are the behavior details for the Promote batch job:
XREF State Before Promote
Base Object State Before Promote
Hub Action on XREF
Hub Action on BO
Refresh BVT?
Resulting BO State
Operation Result
PENDING
ACTIVE
Promote
Update
Yes
ACTIVE
Informatica MDM Hub promotes the pending XREF and recalculates the BVT to include the promoted XREF.
PENDING
PENDING
Promote
Promote
Yes
ACTIVE
Informatica MDM Hub promotes the pending XREF and base object. The BVT is then calculated based on the promoted XREF.
DELETED
This operation behaves the same way regardless of the state of the base object record.
None
None
No
The state of the resulting base object record is unchanged by this operation.
Informatica MDM Hub ignores DELETED records in Batch Promote. This scenario can only happen if a record that had been flagged for promotion is deleted prior to running the Promote batch process.
ACTIVE
This operation behaves the same way regardless of the state of the base object record.
None
None
No
The state of the resulting base object record is unchanged by this operation.
Informatica MDM Hub ignores ACTIVE records in Batch Promote. This scenario can only happen if a record that had been flagged for promotion is made ACTIVE prior to running the Promote batch process.
Promote and delete operations will cascade to direct child records.

0 COMMENTS

We’d like to hear from you!