- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2023 12:39 PM
Hello Experts,
There are some tools in ServiceNow STORE app which are API based integrations/other normal type integrations.
Basically they are not SG connectors, so they dont pass via IRE.
In such scenario, are there any guidelines/best practices to be followed as we are missing the IRE 🙂
TIA!!!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2023 08:41 PM
I mean I'm not trying to be sarcastic when I say that the best practice is to contact the vendor and ask why they aren't using IRE, and consider maybe not using their app if they are not, and building your own integration with that source.
But assuming that you're still not convinced and you're willing to go forward with this integration, I think I should start by pointing out what the accepted "best practice" was considered once upon a time (and you'll still find it cited from time to time). That you should use the correlation_id field to store the unique identifier of the foreign record (e.g. LogicMonitor) that was imported. The main problem with this is that it's only half of the equation. It tells you the record identifier but not the source system that contains that record, and therefore assumes that there is one and only one external source you can use. As long as it's the only external source not using IRE, this may be fine, but if you have multiple sources not using IRE, then they cannot all use the same correlation_id field so you'll probably need to create multiple custom fields to store the various foreign keys. But even after you do this, the problem is that it's not going to play nicely with those sources that are using IRE. As a result this can lead to data collision and/or duplication, i.e. your CMDB is likely to suffer from more and more data integrity issues over time.
Beyond that I don't really know how to answer what are the best practices, because I would need more context. Best practices in what scenario? Bottom line is that the best practice is to use IRE for all data sources in the CMDB, because that is the only way you will get a view of the conflicting sources. For IRE to work properly for any one source, all sources need to be using it. Otherwise the source just isn't playing nice with others.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2023 09:43 PM - edited 10-29-2023 10:01 PM
In order to successfully pass the CMDB Scoped App certification process for NY Apps, it is highly advisable that new developers should follow the best practice outlined in this document and leverage IRE for inserts and updates.
NOTE: It is worth noting that ServiceNow can only certify application that follows the pull mechanism that we have covered above. However, we will not be able to certify the applications that use push mechanism from an external system i.e Leveraging IRE REST API to push CMDB related data from an external system
