Asset Definitions
Since GLPI 11, the generic asset plugin has been integrated into GLPI natively. This makes it possible to create customised asset types to suit your needs.
Migration generic objects to asset definitions
Generic assets migration must be done from the GLPI 10 database. It is not possible to import your assets from GLPI 10 to GLPI 11.
When migrating your instance to GLPI 11, the generic objects plugin must be installed. Once the migration is complete, enter the command in CLI mode from your GLPI folder:
php bin/console migration:genericobject_plugin_to_core
Definitions
Asset definitions can be used to add assets that are not natively available. For example, you can add servers or laptops separately from the native Computers type. Each custom asset could be configured to behave like any other asset via capacities.
Create an asset
To add a new asset, click on + Add;
Fill in the information for the new asset;

Label (this field will appear in the list of assets);
System name (it cannot be changed later);
Comments;
Active;
Icon.
After the creation, an error message appears: There is currently no profile with access to items with current definition You need to go to profiles
Capacities
Capacities lets you add behaviors such as the ability to link software, network ports, contacts, etc. to the asset. Each asset can be selected and customised as required.

List of the behaviors/elements that can be linked:
Antivirus;
Appliances;
Certificates;
Components;
Connections;
Contracts;
Databases instances;
Documents;
Domains;
Financial and administrative information;
Global search;
Historical;
Impact analysis;
Inventory;
Knowledge base;
Manual links / External links;
Network ports;
Notes;
Operating systems;
Plugs;
Projects;
Racks;
Remote management;
Reservations;
Sockets;
Software;
Virtualization;
Volumes.
Fields
The fields tab is used to add additional fields and and hide, or reorder native ones. You can customise them by indicating whether they should be text, URL, date, etc.
Create a custom field
To add a new field, click on + New field;
Fill in the required fields;

Label: name which will be displayed on the asset form, search results, etc;
System name: The system name field corresponds to what will be used when development is involved. Examples: API calls, webhooks, etc. In the legacy API, the field name is prefixed by
custom_
; to avoid conflicts with standard fields;Type: string, date, URL, dropdown, yes/no, text, date and time, number. Cannot be modified once saved;
Full width: indicates the field will be extended along the entire length of the form;
Mandatory: make it mandatory or not to fill in the field before saving the asset;
Readonly for these profiles: select one or more profiles with read-only access to this field. The most restrictive permissions prevail (see profiles);
Hidden for these profiles: select one or more profiles whose fields will be hidden The authorisations in the profiles tab take precedence over this field. It will therefore be visible to a profile even if it is selected in this field;
Default values: specify a default value.
Delete a custom field
It is not possible to delete a field created by default. Only fields added by the user can be deleted. However, it is possible to hide any field.
To delete a custom field, click on the hide icon;

Then, click on the trashbin icon. Note that this action is irreversible

Hide or show a field
Each field can be hidden in the asset form.
To hide a field, click on the hide icon;

To restore an hidden field, drag and drop this field in the list.
Modify a field
You can change all the fields, but some information cannot be changed in a default field.
In a default field, you can modify:
Full width
Mandatory
Readonly for these profiles
Hidden for these profiles

In a custom field, you can modify:
Label
System name (will be modified automatically when changing the label)
Full width
Mandatory
Readonly for these profiles
Hidden for these profiles
Default value

The type of field cannot be modified once it has been saved
Change the order
To change the order of the list of fields, drag and drop your field to the desired position.

Profiles
The profiles tab is used to authorise certain permissions on the assets of this type

You can define the following permissions for each profile:
Create
View all
Update all
Purge
Delete
View assigned
View owned
Update assigned
Update owned
You can add profiles that can associate Server with tickets, problems or changes. This tab allow multiple selection
Translations
You can translate the label and the system name
Click on + New translation;
Select the field to translate;
Select the language;
Indicate the desired translations;
Click on + Add.

Add a new translation
Select the field to translate
Select the language
Fill in the translation fields:
One - the singular form of the label
Many - the plural form of the label
Other - the translation that will appear in the list of assets
All Information
For an item, all information is displayed on one page from the All tab. This shows all of the tabs of an object’s form in one view, one below the other.
Last updated
Was this helpful?