Assets in GLPI 11’s Genericity, do you want to know how you can manage your cats?

 

Well, congratulations, because from now on, in the latest version of GLPI 11, you can create custom assets to manage whatever you want in your GLPI natively. Thanks to a new implementation of assets in GLPI 11’s Genericity.

 

The way Genericity works is quite similar to what we had before with the Generic Objects plugin, but some interesting changes have been implemented that you might want to know about the assets in GLPI 11’s Genericity:

1. It’s no longer a plugin
2. We can decorate our assets with icons
3. Asset permissions are disabled by default
4. The object properties section is now called CAPACITIES
5. Custom fields for assets are now integrated natively
6. The creation of custom dropdowns has changed
7. Asset translations have been integrated
8. Assigning to recurrent tickets

It’s no longer a plugin

As mentioned earlier, in the latest version, object creation is now implemented natively. In GLPI 10, we had to install the Generic Objects plugin.

However, the new Genericity is now implemented in the sidebar under Setup > Asset Definitions.

 

 

From this section, we can create, manage, and configure our assets in GLPI 11, as well as apply our custom settings.

 

We can decorate our assets with icons

 

When creating an object, a new dropdown lets us add an icon to better organise and distinguish our custom assets.

 

 

The icons will appear next to the name of our assets.

 

 

Asset permissions are disabled by default

 

Now, when creating a new asset, permissions are disabled by default, so the asset will not be visible. You need to enable them for the user to be able to view it.

 

 

The object properties section is now called CAPACITIES

Since the new version, to manage the properties of assets, you must go to the Capacities section. In this section, the interface has undergone slight changes, and several new properties have been added, as highlighted in the following image.

 

 

However, not all features from the previous version are present; some have been removed because they are now enabled by default, as shown in the following image.

 

 

Custom fields for assets are now integrated natively

 

From the assets themselves, we now have access to a new section where we can manage custom fields natively, without having to install the Additional Fields plugin. With this, we can create the main types of fields and manage them directly from each of our assets in GLPI.

 

 

The creation of custom dropdowns has changed

With the integration of genericity in asset fields, only the basic functions are natively implemented. To create a dropdown and its dropdown options, we need to create it from the dropdown definitions section and add it to a dropdown field in the asset.

 

 

Asset translations have been integrated

 

Within assets, we have a new translations section that allows us to natively add different translations to assets. When a translation is added and the language is changed, the asset name and its added fields will change accordingly.

 

 

Assigning to recurrent tickets

In GLPI 11, under the Assistance > Recurrent tickets section, a new option has been added to automatically assign items to a ticket that is created periodically.

 

 

What do you think of these new features?

 

In conclusion, the new features of GLPI 11 seem to be very interesting improvements for the users. The new integration of genericity has made the creation and management of assets natively within GLPI much easier. In addition, other important changes have been added, and what caught my attention the most was the icons, even though it’s a purely aesthetic change. I think it’s absolutely necessary to improve the assets interface in GLPI 11.

 

 

If you want, you can continue exploring some implementations, such as the fields integrated in Genericity, here.