Scanning and Automated Discovery

This release includes the following enhancement to Code Insight scans and to the techniques used to discover and report inventory during scans.

Scheduling Multiple Scans on a Project Now Prevented

New controls are now in place to prevent the scheduling of additional scans on a project that is currently in the scan queue or being scanned. If a scan on the your project has already been scheduled or is running, the Start Scan button on the project’s Summary tab is now disabled; you must wait until the current scan is complete before you can schedule another one for the project.

Additionally, the Scan Server Status field occasionally does not update quickly enough to reflect the “Scan scheduled” or “Project being scanned” status. However, if a scan on the current project is already in queue or running, an attempt to click the field’s “here” link to schedule a scan will result in an error message, stating that you cannot start another scan on the project. For your reference, the message also provides the task ID for the currently queued or running scan. This ID can be used with the Get Scan Status API to check the scan status outside of the UI when necessary.

These same controls are place for the POST method of the Project Scan API. See Updates to Existing APIs.