'On matching process' is a parameter in the table configuration. In this use case, 'On matching process' is set to 'Yes' to ensure matching execution.
When a record is created, matching automatically enforces a match against the table. This matching process uses records with unmatched, suspect, pivot and golden states only. 'To be matched' records are not used because they are processed by the 'match at once' operation. Any 'Suspicious' records are not used because they require a human decision. Any 'definitive golden' records are no longer matched. Records with 'merged' and 'deleted' states no longer hold matching value.
The result of this matching is one of the following:
Golden record in the '001' cluster.
Golden record in a non-predefined cluster. This implies a golden record that underwent an automatic merge.
Suspect record in a non-predefined cluster.
Pivot record in a non-predefined cluster.
Merged record in a non-predefined cluster.
When 'simple matching' is configured then the possible results are:
Suspicious record in the '004' cluster.
Golden record in the '001' cluster.
When a record is modified:
The modification of a 'to be matched' record does not result in a matching operation.
The modification of a golden, suspect, pivot, unmatched or suspicious record results in a matching operation against the table (same as for the creation).
The modification of merged and deleted records is not permitted.
When a record is deleted its state is set to 'deleted' and it stays in its current cluster. This is a logical deletion only.
'On matching process' is a parameter in the table configuration. In this use case 'On matching process' is set to 'No' to disable matching execution.
When a record is created, the matching sets its state to 'unmatched' and places the record in the '000' cluster. Matching is not executed.
When any field of a record is modified, the matching sets its state to 'unmatched' and places the record in the '000' cluster. Matching is not executed.
The add-on executes the same operation as the one used when the 'matching process' parameter is active. This means that the record's state is set to 'deleted' and it stays in its current cluster.
When a table under add-on control is not configured or faces trouble with its process or matching policy (impossible to match any field due to error in the matching configuration), then the matching runs as if the 'On matching process' parameter were set to 'No'.