Service Graph Connector not creating duplication tasks

[Joshua Comeau]

Looking into Service Graph Connector does it create de-duplication tasks?

If so, how as my current setup is not doing so and wondering how to setup the Identification reconciliation rules as well as how to remediate the duplications on per example workstations, please assist on better understanding the issue at hand.

Note I have successful setup up SGC as it is currently importing the data. Now looking into on how to clean up the date with the use of SGC.

Thank you everyone!

[Sohail Khilji]

Hi @Joshua Comeau ,

You can create workflow to remidate de-duplications and associate it to a deduplication task.

[Joshua Comeau]

How? Should SGC already do this? is this with the legacy workflow or flow designer?

[Sohail Khilji]

The de-duplicate task got created due to cmdb remediation rules 

You can find them by navigating to Configuration > CMDB Remediations

Also if you want tasks to assign to a particular group, you can do so by creating a workflow and adding it to the rule.

Please make the answer helpful or correct if it helps....

[Ashok Sasidhara]

Service Graph Connector goes through the IRE. So ideally it should have created de-duplication tasks. For each CI class populated by your SGC, first check whether duplicates have got created for that class. Its a possibility that duplicates itself may NOT have got created (although its a rare scenario and might typically happen only if you have less number of records populated so far). 

Also check if the information in the following URLs are helpful for analysis:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0726425

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0712338

If the above-mentioned analysis does not help to identify the reason, please raise a hi-ticket.