Custom Non-CMDB Table to use with IntegrationHub ETL?

adb-bbird
Tera Contributor

Hi all,

 

Hoping someone can help me out. I'm attempting to make a custom Service Graph Connector and am looking at the possibility of associating a CI Class in IntegrationHub ETL with a custom Non-CMDB table contained in my Scoped Application. I know for example that I can add a class "Software Instance", which is Non-CMDB class, and then associate it with a defined CMDB CI class in my ETL. What I'm curious about is how, if it's at all possible, do you add a custom Non-CMDB table to the dropdown for IntegrationHub ETL. 

 

The requirement is that I want to capture some details that are not attributes of the CMDB CI being discovered. So, in this example, I would discover and create a "Computer" CI, and then have an associated Non-CMDB record created with the additional details only relevant to the Service Graph Connector. There are reporting reasons why this is relevant and why we want to have this data in its own table.

 

Any thoughts on where I can look, is this even possible, or if I'm potentially thinking about this the wrong way?

Thanks!

1 ACCEPTED SOLUTION

Sandeep90
ServiceNow Employee
ServiceNow Employee

@adb-bbird  One way to achieve this is you first need to define a related entry rule on the cmdb ci class that you want to associate non-cmdb class with, this means the non-cmdb class should have the reference to the cmdb class. Once its setup then you can configure in the similar way as you defined for the software instance class. 

View solution in original post

2 REPLIES 2

Sandeep90
ServiceNow Employee
ServiceNow Employee

@adb-bbird  One way to achieve this is you first need to define a related entry rule on the cmdb ci class that you want to associate non-cmdb class with, this means the non-cmdb class should have the reference to the cmdb class. Once its setup then you can configure in the similar way as you defined for the software instance class. 

That was it!! Thank you so much! For additional information for anyone that may stumble across this thread, I had to create a new cmdb related entry on the "Related Entry" table (cmdb_related_entry) for the targeted cmdb ci class. This allowed me to choose the non-cmdb class to associate in my IntegrationHub ETL. Thanks @Sandeep90