Stop de-duplication tasks

[A Westervelt]

We switched over from the legacy CI identification scripts to the new Identification and Reconciliation engine for the CMDB. At first, the de-duplication tasks we useful and pointed out a few errors that we had. However, every false positive keeps reappearing and the usefulness has become a needle in a haystack.

Is there a way we can still use the Identification and Reconciliation, but not generate the de-duplication tasks anymore within Helsinki? Or will I have to migrate back to the legacy identifiers?

[bernyalvarado]

Hi Andrew,

here goes what the documentation states:

Skip duplicationProcessing of sets of duplicate CIs depends on the system properties glide.identification_engine.skip_duplicates
 (set to true by default) andglide.identification_engine.skip_duplicates.threshold
 (set to 5 by default), and on the number of duplicate CIs in a set.
If glide.identification_engine.skip_duplicates is true, and the number of duplicate CIs is less than the threshold specified byglide.identification_engine.skip_duplicates.threshold, then the oldest of the duplicate CIs is picked as a match and gets updated. The rest of the duplicate CIs are tagged as duplicates by setting the cmdb_ci's discovery_source field as 'Duplicate'.
If glide.identification_engine.skip_duplicates is false, then matching of duplicate CIs fails with an error, and none of the duplicate CIs is updated.

Note: In either case, de-duplication tasks are always created.

To modify these properties, you need to first add them to the System Properties [sys_properties] table. For more information, see Properties installed with Identification and Reconciliation.

Thanks,

Berny

[bernyalvarado · Accepted solution]

The source of the above is: https://docs.servicenow.com/bundle/helsinki-it-service-management/page/product/configuration-managem...

There's still an option though... and that will be to create an onBefore insert business rule within the task table and have it abort the insert whenever you identify a de-duplication task.

Thanks,

Berny

[bernyalvarado]

The clause to abort the insert within the business rule is:

current.setAbortAction(true);

Thanks,
Berny

[A Westervelt]

It's so simple, I didn't even think of this as an option to do the abort action on the reconcile_duplicate_task table. Thanks!