Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
Hi there,
The Australia release introduced four new Instance Scan related System Properties. Two of them are directly related to Parallel Scanning and were already covered in my article on Australia's Parallel Scanning. The other two properties are documented on the ServiceNow Docs, though they don't appear to be mentioned in the Australia release notes. As a result, there's a good chance many Instance Scan enthusiasts will completely miss them.
Let's take a closer look!
New System Properties in Australia
The Australia release introduced four new Instance Scan related System Properties. In this article we will be focusing on the first and last one, "glide.scan.inactive_records" and "glide.scan.base_system_records".
glide.scan.inactive_records
The first new System Property is "glide.scan.inactive_records".
Instance Scan used to only evaluate active records when using a Table Check, Column Type Check or Linter Check. With the Australia release new System Property "glide.scan.inactive_records" has been introduced. When enabled, inactive records are included when performing a scan.
The System Property has a default value of false.
Pretty straightforward. This property is present by default on new and upgraded Australia instances and can be modified by any user with write access to System Properties.
Perhaps you already noticed I did not mention the Script Only Check. That's because Script Only Check doesn't evaluate records in the same way as Table Checks, Column Type Checks and Linter Checks. Instead a Script Only check scans everything the scan engine has access to and that falls in your query, regardless of whether a record is active or inactive.
glide.scan.base_system_records
The second new System Property is "glide.scan.base_system_records".
When using Table Check, Column Type Check or Linter Check, non-customized base system records would be ignored while scanning. In cases you would want non-customized base system records to pop-up, as workaround you could create a Script Only Check. With the Australia release new System Property "glide.scan.base_system_records" has been introduced. When enabled, non-customized base system records are included when performing a scan.
Pretty straightforward. Note that this property is not present by default on new and upgraded Australia instances though it can be added with a value of true to enable it.
When enabling this System Property, do be aware that the scans you are performing (and also the scheduled out-of-the-box ones) will generate a significantly larger number of Scan Findings!
Here an example of Scan Check "Review Public UI Pages" which suddenly comes with 62 Scan Findings when scanning of non-customized base system records is enabled.
---
That's it. Hope you like it. Finally I finished this article, it was already pending for a while 😅. If any questions or remarks, let me know!
| C |
If this content helped you, I would appreciate it if you hit bookmark or mark it as helpful.
Interested in more Articles, Blogs, Videos, Podcasts, Share projects I shared/participated in? |
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
11x ServiceNow MVP
---