Asset templates and report context

Templates describe the expected structure of a workstation or unit. When an asset is linked to a report, ReportArea preserves both an opening snapshot and its authorized current state.

Availability: templates for asset managers; asset selection for assigned users and staff handling reports. Level: Advanced.

Purpose

Use templates to repeat consistent structures, define component positions, and set compatibility rules. Use report context to identify the exact asset, installed component, or empty position that requires attention.

Requirements

Create component types before using them in a template.
Have Manage assets to create, edit, or publish templates.
Only published revisions can be used to create assets.
To link or correct assets on a report, the report must be active and the user must be authorized.

Templates step by step

Define component types and their relevant fields.
Create a template and edit its draft.
Add positions as a tree, including type, parent, maximum quantity, and compatibility rules.
Publish the revision. It becomes immutable.
To change it, create a new revision. Existing assets stay on their earlier revision until an assisted adoption.
During adoption, decide how to map or remove every existing component that no longer fits.

Report context

When a report is created, active assets assigned to the creator are preselected and can be removed.
Zero or more exact components or empty positions can be selected, including parent and occurrence where needed.
The report saves a full snapshot of the structure when attached.
While it remains active, the creator and authorized staff can correct assets or selections; staff must enter a reason.
The detail separates When the report was opened from Current state. Removing and adding an asset again creates a new link and snapshot without overwriting the earlier one.

Rules and effects

A published revision cannot be edited.
A template supports up to 200 positions and five component levels; every position is optional within its maximum.
Adoption preserves installation history.
Users assigned to the asset, contextual staff, and authorized managers see the needed detail. Other participants see a reduced snapshot without internal codes, serial numbers, identifiers, or sensitive specifications.
A targeted request uses the asset's current state and keeps its target in report history.

Required and optional information

Required: template name and identity; type for each position; a valid structure before publication; a reason when staff corrects report context. Optional: positions, compatibility rules, selected components, and assets attached to the report.

Practical example

An “Office PC” template defines a motherboard, memory, and storage. A report selects Ana's PC and the empty second memory position. Even after a module is installed, the report retains the opening snapshot and shows the current state separately.

Current limits

Assets do not automatically move to a new revision.
Cycles and structures beyond depth, position, or installation limits are rejected.
Participants without live technical access do not see internal identifiers or specifications.
Custom graphics for templates are not supported.