An asset’s validation progress shows three stages: Due → Requested →
Validated. A request can additionally turn Overdue or Rejected.
Requesting is only possible once all seven core fields are set — see
Capturing ITAM Data.
Walking Through a Validation
The available button depends on the status:
A context line below the progress shows date, editor, and — for Rejected —
the reason. For Due the line is omitted. How long a validation remains
valid is set by the Validation Cycle (Days) setting — see
ITAM Fundamentals. While you are editing ITAM data, the validation actions are blocked, not
hidden. Save or discard your changes first.
Validating Several Assets at Once
In the ITAM › Assets list, mark rows and choose Validate or Reject.
Both actions are only available when every selected row carries the status
Requested or Overdue — if the selection contains other statuses, the
action is blocked.
The five status filters — Validated, Due, Requested, Overdue, and
Rejected — select matching cases together: filter on Requested, mark
everything, validate in one pass.
Strict Mode
If Strict Mode is active, permissions are split between two roles: the
Asset Owner may Validate and Reject; the Technical Owner may
Request, Request Again, and Revoke Rejection. If either role is not
set on the asset, nobody can perform the respective step.
