Instance scan continued - Useful methods for Script Only Checks

[ChrisF323949498]

Previously I wrote about Instance Scan and how I feel its under utilised, and you and your teams could likely benefit from it.

Now let's dive into some more specifics on the use of 'Script Checks', and a few important methods to use.

1. finding.increment() - This will essentially tell the health check 'Hey we found a(nother) instance of this issue, so increase the count'.
   That count will then be displayed in the 'Scan findings' area of the tool, column: 'Count'.
2. setCurrentSource(glideRecord) - This will then show in the results, giving you a direct link to the 'offending' record which failed the health check. 

The above 2 are critical to use, as they add the vital information to resolve the issues the scans locate.

Note: Older checks seem to be given a 'finding' parameter whilst newer checks seem to default with a templated function parameter of engine: 

(function(engine) {})(engine)

If you're working with the engine parameter, you'll need to use:

	engine.finding.setCurrentSource(gr);

However the are others lesser well known Methods (I've not found any official documentation, so use at own risk 😄

engine.finding.setValue('finding_details', "Table Name:" + yourVariableInYourScript);

This will populate the 'finding Details' column on the scan findings table (scan_finding_list) allowing you to give your end users more specific finding details. 

In future posts we'll jump into further details on lesser known methods and explore what else we can use instance scan for.

Have a great day!