Add new data

Used to add data by using the following approaches:

Through the load process
By using the Data Manager
Through the API verb using PUT or CLEANSE_PUT through protocols such as HTTP, SOAP, and EJB.

Add new pending data

A record is created with the PENDING state. Applies to state-enabled base objects.

Update existing data

Used to update data by using the following approaches:

Through the load process
By using the Data Manager
Through the API verb by using PUT or CLEANSE_PUT through protocols such as HTTP, SOAP, and EJB.

If trust rules prevent the base object columns to be updated, no message is generated.

Update existing pending data

An existing record with a PENDING state is updated. Applies to state-enabled base objects.

Update, only XREF changed

Used to update data in the following scenarios:

When only the cross-reference has changed through the load process
When only the cross-reference has changed through the API using PUT or CLEANSE_PUT through protocols such as HTTP, SOAP, and EJB.

Pending update, only XREF changed

A cross-reference record with a PENDING state is updated. Also, includes the promotion of a record. Applies to state-enabled base objects.

Merging data

Used to merge data by using the following approaches:

Through Merge Manager
Through the API Verb through protocols such as HTTP, SOAP, and EJB.
Through the Automatch and Merge process

Merging data, base object updated

Used to merge data in the following scenarios:

When the base object is updated
When records load by row ID to insert new cross-reference and the base object is updated

If trust rules prevent the base object columns to be merged, the MDM Hub does not generate any messages.

Unmerging data

Used to unmerge data by using the following approaches:

Through the Data Manager
Through the API verb by using UNMERGE through protocols such as HTTP, SOAP, and EJB.

Accepting data as unique

Used to accept records as unique by using the following approaches:

Through the Merge Manager
Through the Schema tool by enabling the option when you configure match rules

When a record is accepted as unique, either automatically through a match rule or manually by a data steward, the MDM Hub generates a message with the record information, including the cross-reference information for all output systems. The message is placed in the queue.

Delete base object data

A base object record is soft deleted and the state is changed to DELETED. Applies to state-enabled base objects.

Delete XREF data

A cross-reference record is soft deleted and the state is changed to DELETED. Applies to state-enabled base objects.

Delete pending BO data

A base object record with a PENDING state is hard deleted. Applies to state-enabled base objects.

Delete pending XREF data

A cross-reference record with a PENDING state is hard deleted. Applies to state-enabled base objects.

Restore

A deleted cross-reference record is restored and the state is changed to ACTIVE. Applies to state-enabled base objects.