- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2018 04:17 PM
CMDB Dashboard > CMDB View
I am trying to learn the logic behind the Duplicate CI's widget. How the Duplicate CI's work?
If anyone knows please share it with me.
Thanks,
Rajini
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2019 12:28 PM
The duplicates on the CMDB Dashboard are derived from CIs that are tagged with the discovery source field of duplicate. When this happens, a de-duplication task record is created listing or grouping all the duplicate CIs.
A CI is tagged as a duplicate either during ServiceNow discovery. During the identification phase, the IRE (hardware rule) is used to identify if the CI exists or does not exist in the CMDB to determine if an update or insert should occur. If multiple CIs exist in the CMDB as identified by the Hardware rule, then the oldest CI (in terms of creation date) is updated and its discovery source is defined as ServiceNow, however the other duplicate CI is not updated and its discovery source is flagged as duplicate. As a result of this process, a de-duplication task is created and the two CIs will display on the CMDB Dashboard under the Correctness Scorecard only after the Correctness scheduled job is run.
A second scenario exists if a duplicates exist in the CMDB and CIs do not have any discovery source defined. In this case, after the Correctness schedule job is run, these CIs will be added automatically to a de-duplication task record and also automatically be part of the calculation on the Correctness Scorecard.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2019 12:28 PM
The duplicates on the CMDB Dashboard are derived from CIs that are tagged with the discovery source field of duplicate. When this happens, a de-duplication task record is created listing or grouping all the duplicate CIs.
A CI is tagged as a duplicate either during ServiceNow discovery. During the identification phase, the IRE (hardware rule) is used to identify if the CI exists or does not exist in the CMDB to determine if an update or insert should occur. If multiple CIs exist in the CMDB as identified by the Hardware rule, then the oldest CI (in terms of creation date) is updated and its discovery source is defined as ServiceNow, however the other duplicate CI is not updated and its discovery source is flagged as duplicate. As a result of this process, a de-duplication task is created and the two CIs will display on the CMDB Dashboard under the Correctness Scorecard only after the Correctness scheduled job is run.
A second scenario exists if a duplicates exist in the CMDB and CIs do not have any discovery source defined. In this case, after the Correctness schedule job is run, these CIs will be added automatically to a de-duplication task record and also automatically be part of the calculation on the Correctness Scorecard.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2019 11:40 PM
Hi glennpinto,
thanks for the information,
what will happen for corresponding Asset Record from (alm_hardware). which is/was created during discovery.(BR triggered to create asset record).
i have set Non-Operation status while remediation of de-duplication task. and nothing changed in asset record status.
OR which filed/attribute needs to use if i want to update status for ci same time when i complete de-duplication task.(any attribute which runs in sysnc on both table)
i dont want to delete any ci record from CMDB.
thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2025 09:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2022 01:39 AM
Hi,
Can we exclude any class for de-dup Task create ? e..g. if i dont want de-dup task to be created for Windows Class how can we stop that ?