Normalize for ServiceNow - CI Verification/Merge CI
Has anyone used the CI Verification in ServiceNow and merged CIs? Does anyone know how the Data Platform will handle the change to the unique identifier (i believe its the correlation ID) from ServiceNow when it changes?
I tested the feature in a standalone instance when two CIs are merged, and I found that the Correlation ID is replaced with the newest CI's correlation ID.
WIll the Data Platform update the mapping of the existing records with the correlation ID or create another record in its database? Will the old record get deleted from the Data Platform (since it couldn't be found in the data source) and then create a new record?