Assets
Under the menu item Assets you will find the Configuration Management Database (CMDB), i.e. the KIX asset database. All equipment and equipment information required for service provision is managed here. This can include locations, buildings, rooms, machines, hardware and software, as well as telephones, small devices and contracts.
Fig.: Schematic asset database > asset classes > assets
All these resources are created in the system as so-called assets . In order to map these assets in a structured manner, they are assigned to different asset classes. The characteristics of the asset classes are flexible and depend on the respective use case. They differ according to their properties (attributes). KIX offers a range of existing asset classes in the delivery state Asset classes are also referred to as config item classes, CI classes, and in ITIL also as "CI types".
Changes to asset classes and their attributes are recorded in class definitions. These definitions are subject to versioning. Changing the attributes of an asset class has no destructive effect on inventory data. These are retained in their previous form and content.
Changes to the asset information are historicized and also versioned. It is possible to look back at a previous version of the asset information at any time, regardless of whether the referenced asset class definition is out of date or not.
The authorization check when accessing assets is carried out in accordance with the authorization concept. Access to assets requires access rights to the "configitems" resource and to the asset itself. Therefore, at least the "Asset Reader" role is required.
Tip
If you prefer the term "Config Items" or "CI" instead of "Assets", you can enter a pattern for this in the menu → and thus change the name in the system.
You can link assets to tickets specifically and automatically. To do this, use the event handler . This is an addition to the system monitoring integration via mail filter.
It enables a targeted search for assets based on asset-identifying information stored in articles (especially emails) or fields, such as IP addresses or FQDNs. The specific attributes of the asset classes are used as search criteria and searches are only performed in matching asset classes
The e-mail filter for system monitoring has some limitations in this respect:
It can only perform a simple asset search based on the asset name.
He cannot assign multiple assets to the ticket to be created.
It cannot react to further, different article attachments or subsequent setting of form fields.
The automation is also not tied to incoming articles by email. It can therefore also respond to inboxes from other channels, such as the Self Service Portal or input in a text form field by agent users.
The configuration is carried out in the following SysConfig keys (menu → ):
Note
Follow the instructions in the respective keys.