The Scan History lists every code-analysis run the Configuration Checker has carried out, across all accounts. Use it to check whether a scan completed, compare a run against earlier ones for the same asset, and download the report a run produced.
Location and Permissions
Path in UI:
PlatformManager > Administration > Configuration Checker > Scan History
-
View the history and download a report:
Configuration Checker Assets - readorConfiguration Checker Assets - edit(global permission). -
Start a manual scan:
Configuration Checker Assets - edit(global permission).
These are the same permissions that control the Asset Registry, so an account that can read the registry can read the scan history.
Scan History Table
The table shows one row per scan run. You can filter and sort the rows, and each filter offers an All entry to clear it.
|
Column |
Description |
|---|---|
|
Account |
Customer account the scanned asset belongs to. |
|
Implementation Partner |
Implementation partner associated with the account, so a scan result can be attributed to the partner that configured the asset. The value is synchronized from Salesfx together with the other account-level information. |
|
Asset |
Identifier of the scanned asset: the partition or the provisioned IntegrationManager instance. This is the same identifier as the Asset ID column of the Asset Registry. |
|
Type |
Partition or Integration. |
|
Status |
State of the run: Pending, Processing, Completed, or Failed. A report can be downloaded only for a Completed run. |
|
Cached |
Yes or No. Yes means the run reused the result of an earlier analysis instead of analyzing the code again. This happens when the code has not changed since a previous scan. A cached run reports the same findings as a fresh one, and it finishes faster. Filter the column to compare cached and freshly analyzed runs. |
|
Duration |
How long the run took. |
|
Score |
Overall score the run produced for the asset. |
|
Critical, Major, Minor |
Number of findings at each severity. Critical findings must be fixed, Major findings are suggested to fix, and Minor findings are for information. |
|
Message |
Additional information about the run. For a failed run this is where the reason appears. |
|
Started By |
Who started the run. A scheduled scan and a manually started one are distinguished here. |
|
Started At, Finished At |
When the run started and finished. Runs are ordered by Finished At when the most recent completed run is selected. |
The Cached column also appears on the code-analysis lists for a single asset. You reach those from Show Reports on an asset in the Asset Registry, and from the Code Analysis section of the partition or integration overview.
Downloading a Report
Open the row menu on a scan and select Download report to download the report the run produced, as an HTML file. The report is available only for a run whose status is Completed.
The latest report for an asset can also be downloaded programmatically through the PlatformManager public API. The endpoint is published in the Swagger UI of your environment, under public-api.
Starting a Scan Manually
Scheduled scans run according to each asset's scan frequency, set in the Asset Registry. To scan an asset immediately, use Run code scan on the asset in the Asset Registry. A manual scan is possible only for an asset that is still registered and active: an asset removed from PlatformManager cannot be scanned again, although its earlier runs stay in the history.
See Also
-
Asset Registry – Which assets are scanned, how often, and who owns them.
-
Rule Sets – The rule sets the scans apply.