Skip to main content
Version: 0.10

Reviewing a scan

Most scans need nothing from you: they collect, match what they found to existing assets, and write the changes. Two situations stop a scan until someone acts:

  • Needs review: some changes could not be matched to an asset with certainty. You decide where each one belongs.
  • Awaiting approval: the template's action settings hold the run's changes until someone approves them.

This page describes the run page and both situations. For stages and states in general, see Scanning.

Opening a run​

Open Scans → History and select a run, or follow a scan notification. The run's page shows the template name as its title and Run <id> above it. The header offers:

  • Run again: starts the same template once more (for a template that scans a file, it asks for the file first);
  • Delete run: removes the run, its findings and its changes from history. Assets it already created or updated stay; nothing is rolled back;
  • Back to history.

Under the header, a callout states the run's state in one sentence and holds the action that state calls for. For Needs review and Awaiting approval it is highlighted, because the run will not move until someone acts. A failed run is highlighted too.

The page has three tabs.

Overview​

A summary strip with Started, Finished, Duration, Template, Integration, Findings, Changes and Assets touched (new and updated), followed by the Pipeline: the nine stages, with the failing, current or last stage's log open. Any stage that wrote a log can be selected to read it.

Results​

Results (N) lists what the scan would change in the inventory, one row per change entry. This is the tab you work in when a run needs you.

ColumnMeaning
StatusWhether the change is settled, see Status of a change
ActionWhat the change does, see What a change does
Identified assetThe asset the change applies to. Shows New asset for a creation, the number of candidates (for example 2 candidates) while the choice is still open, or No match. A settled asset name links to the asset
Field columnsThe fields the integration produced for this change

The field columns are grouped in the Columns menu by where each field comes from (the integration's own fields, or shared asset fields). The column choice is kept in the page address, so a view can be shared as a link.

Above the table you can search within the changes and filter by Status and Action. The table shows 10 rows per page by default; 20 and 50 are available, but larger pages load noticeably slower because each change carries its full matched asset.

Select a row (or Inspect the change in its menu) to see it in detail:

  • Fields lists each field the change would write, its value and its mode: Merge adds to what is already there, Replace overwrites it, and Do not override only fills a blank field.
  • Raw record shows the source record the change came from, formatted, with a copy button.

Findings​

Findings (N) lists every raw record the sensor collected from the integration's source, exactly as it arrived, before Velum Edge made anything of it. Each row shows the Finding id, its processing State (Not processed, Processing, Processed or Discarded), its Source within the upload, and a preview of the Record. Select a row to read the full record.

Use this tab when a change looks wrong and you want to know whether the source sent wrong data or the scan read it wrongly.

What a change does​

Action (as the console shows it)Effect when synced
Create assetA new asset is created from the change's fields
Update assetThe identified asset is updated with the change's fields
IgnoreNothing is written for this record

The template's Actions settings can still affect the outcome at sync time: with On New Asset Discovered set to Ignore, Create asset changes are counted as ignored instead of creating assets.

Status of a change​

StatusMeaning
Needs reviewThe scan could not decide which asset this record belongs to, typically because it matched more than one existing asset. The run stops until every such change is resolved
Auto resolvedThe scan matched the record by itself
Resolved by handSomeone resolved or changed it on this page

Resolving conflicts​

When a run is in Needs review:

  1. In the callout, select Review changes. The Results tab opens, filtered to changes that need review.
  2. On each row, select Resolve this change. The dialog lists the existing assets the scan matched, each with its OS, private IP and last-seen time where known. Select a candidate's name to open that asset in a new tab without losing the dialog.
  3. Choose one of:
    • Select this asset on a candidate: the change updates that asset;
    • Create a new asset: the record becomes a new asset;
    • Ignore this change: nothing is written for this record.
  4. When every conflict is resolved, select Resume analysis in the callout.

Resume analysis checks the run again. If any change still needs review, the run stays in Needs review. Otherwise it continues to Validation, and from there either to Awaiting approval (if the template holds changes for approval) or straight to syncing.

An update can only be pointed at one of the candidates the scan found. To put the record on a different asset, create it as a new asset and merge afterwards, or ignore it.

Discarding a change​

While a run is in Needs review or Awaiting approval, any row's menu offers Discard this change. The change is removed from the run and will not be applied. The raw record it came from stays on the Findings tab, and a later run of the template will propose it again if the source still reports it.

In other states the run's changes can be inspected but not changed.

Editing a change

The console does not edit a change's field values. To correct a field the source gets wrong on every run, add a rule to the template. To change where one change lands, resolve it as described above.

Approving a run​

A run goes to Awaiting approval when its template's Actions settings ask for it and the run has something to approve:

  • On New Asset Discovered is To Approve and the run would create at least one asset; or
  • Existing asset updated is To Approve and the run would update at least one asset.

Review the Results tab, discard any change you do not want, then select Approve changes in the callout. The run moves on to syncing and writes every remaining change into the inventory. Approval applies to the whole run; there is no approval per change.

There is no reject button. To reject everything a run proposes, delete the run. Its changes go with it and no asset is touched.

"Verification required" notifications​

When a run first stops in Needs review, Velum Edge sends a Verification required notification (warning severity) to the tenant's notification centre. It links to the run. Resolving the conflicts and resuming does not send a second one.

A run that goes to Awaiting approval sends no notification. If your templates hold changes for approval, check Scans → History with the Awaiting approval filter. See Notifications.

Waiting runs are not kept forever

A run waiting in Needs review or Awaiting approval counts towards the tenant's scan history limit (50 scans by default) and is deleted once enough newer scans exist. See Scan history retention.

Permissions​

Resolving, discarding, resuming and approving need the Scan results (Write) permission. Run again and Delete run need Task results (Write). See Roles and permissions.

See also​