Skip to main content
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.
Reject requires a reason: No longer responsible, Asset not found, Data incorrect, or Other with a free-text field. Revoke Rejection conversely requires a mandatory justification for the reversal.

​
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.
For a multiple selection, the ITAM › Assets list does not check in advance whether you are the Asset Owner of every selected asset. If you are not for one of them, Docusnap365 rejects the action; the message names the role that may perform it. The same applies on a single asset when an owner was changed after you opened the page: the buttons still reflect the roles before the change. Validated assets are the basis for warranties and costs.