<literal>NameKey</literal> *
type: Content of: <chapter><sect1><variablelist><varlistentry><term>
<literal>Key</literal> *
Context English German State
All hardware components not classified as computers, possibly ranging from a "blade center" chassis to printers and USB sticks, depending on the level of granularity of your CI structure.
[ Network ]
[ Netzwerk ]
Logical networks (LAN, WLAN, WAN etc.), which span IP address spaces.
[ Software ]
[ Software ]
All software products and licenses.
Alle Softwareprodukte und -lizenzen.
[ Locations ]
[ Standorte ]
All Locations, e.g. building, workplace, IT facility.
Alle Standorte, z.B. Gebäude, Arbeitsplatz, IT-Einrichtung.
If the five classes do not suffice to describe your IT environment, further classes can be added via the "general catalog" link in the OTRS::ITSM admin area. After creating a new CI class in the general catalog, a definition must be entered in ConfigItem.
<graphic fileref="screenshots/admin-general-catalog-management-class.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
<graphic fileref="screenshots/admin-general-catalog-management-class.png" scalefit="1" width="100%" contentdepth="100%"></graphic>
The design of a CMDB data model and of the associated CIs is a task which should not be underestimated. Our experience shows that it is highly recommendable to validate conceptual thoughts in a dry run against the existing IT infrastructure, before changing the OTRS::ITSM standard data model and/or CI classes. It has proven to be of value to resort to external assistance, e.g. of ITIL practice experts for the CMDB design.
Multiple input field types can be used when defining a class. These input field types are used to generate the edit form for creating new or editing already existing configuration items.
Since version 6.0.18 the configuration item class definitions have to be written in YAML format.
The following block is an example of a form field called <emphasis>Operating System</emphasis>.
- Key: OperatingSystem
Name: Operating System
Type: Text
Size: 50
MaxLength: 100
The following settings are available when adding or editing this resource. The fields marked with an asterisk are mandatory.
<literal>Key</literal> *
Must be unique and only accept alphabetic and numeric characters. If this is changed, data will not be readable from old definitions.
<literal>Name</literal> *
The label of the field in the form. Any type of characters can be entered to this field including uppercase letters and spaces.
It is recommended to always use English words for names.
Names can be translated into other languages with custom translation files. See the <ulink url="">Custom Translation File</ulink> chapter in the developer manual.
Defines whether the field is searchable or not. Possible values are <emphasis>0</emphasis> or <emphasis>1</emphasis>.
<literal>Input</literal> *
Initiates the definition of the input field. An input field can contain the following attributes:
<literal>Type</literal> *
Defines the type of the element. Must be placed indented as a logical block. Possible values are:
<literal>Text</literal>: A single text field.
<literal>TextArea</literal>: A text field with multiple rows.
<literal>GeneralCatalog</literal>: A drop-down list for select a general catalog class. The general catalog class must be defined before use it as input type. The items of the general catalog class will be the options of the drop-down list.
<literal>CustomerCompany</literal>: A drop-down list for select a customer from the database back end.


No matching activity found.

Browse all component changes


English German
No related strings found in the glossary.

Source information

Source string comment
type: Content of: <chapter><sect1><variablelist><varlistentry><term>
No labels currently set.
Source string location
Source string age
9 months ago
Translation file
i18n/, string 941