instance scan checks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2024 10:01 PM
Hi
This is my requirement :-
"It is not allowed to write into the "sys_object_source" table.
Prior to Orlando, this table gets internally populated by discovery/SCCM.
From Orlando and onwards sys_object_source table will get internally populated [populates based on the IRE’s createOrUpdateCIEnhanced API] only by IRE itself and used to do optimized IRE matching.
Creating/Updating entries directly in this table, can potentially lead to duplicate CIs getting created.
Additionally, This table gets internally used for licensing purposes and should not be allowed to be populated externally/manually.
Below are ways that might be helpful in identifying the code related to the object source table:
GlideRecord/GlideRecordSecure on sys_object_source
By using sys_object_source table API
Initializing global script include: ObjectSource
Recommendation : Remove the code related to sys_object_source from application and use IRE."
I don't understand what are these sources?
where these type of API's store ?
what type of check i should do?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2024 06:20 AM
Hi there,
See the below topic for the correct answer:
https://www.servicenow.com/community/developer-forum/instance-scan-column-type-check/td-p/2790326
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field