Configuration Item

Modified on Tue, 6 Oct at 11:48 AM

A Configuration Item (CI) is the companion record that sits behind every Hardware Asset and carries its Category-specific Custom Fields. Think of the Hardware Asset as the "master record" (who has it, where is it, what does it cost) and the Configuration Item as the "technical details record" for that same physical item.


TABLE OF CONTENTS



Overview

Configuration Items are a separate entity in the data model, but in practice every Hardware Asset owns exactly one Configuration Item.


Fields

  • Name
  • Description
  • Notes
  • Additional Properties – the actual Custom Field values for this item.
The CategoryId value you sometimes see on a Configuration Item is only used to look up which Custom Field definitions apply — it is not a stored relationship on the Configuration Item itself.



Automatic Creation

When a Hardware Asset is created or updated without an existing Configuration Item linked, au2mator creates a new, empty Configuration Item automatically and pre-fills every Custom Field that is defined on the asset's Category with an empty value.


Category Based Custom Fields

The actual list of Custom Fields that show up on a Configuration Item comes from the Category of the linked Model. Different Categories (e.g. Notebook vs. Monitor) can define completely different sets of Custom Fields.


Relationship to Hardware Asset

A Configuration Item is always reached through its Hardware Asset; it is not meant to be created or managed independently of one.


See also: Hardware Asset, Category



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article