Some of the lists on forms, such as the Type of hardware asset, can be modified. Depending on the list you can modify the names of existing values, create new values, and add children to values. For example, under the computer type of a hardware asset you could add server, desktop and laptop as children. You may also add your own types, such as a new hardware asset type called server.
Some lists have values that cannot be modified because they are in a sealed management pack, while others are in an unsealed management pack so they can be modified. But if you choose to modify the names of existing values or delete the existing values, your changes will be overwritten when you upgrade to a new version of the IT Asset Management Pack. Any customizations, however, are kept when you upgrade.
The following lists can be modified (Library workspace, Lists folder):
Agreement Life Cycle Status
Contract Time Frequency
Cost Event - Agreement
Cost Event - Hardware Asset
Hardware Asset Disposal Reason
Hardware Asset Life Cycle Status
Hardware Asset Type
ITAM Service Requests Submit by Type
Product Usage Rights - Language
Product Usage Rights - Region
Purchase Order Life Cycle Status
Purchase Order Line Item Status
Software Manager Type
User defined agreement type
When adding types that need to be saved in an unsealed management pack, the best practice is to save them all in the same custom management pack. You will be prompted when a type needs to be saved in an unsealed management pack.
Other considerations are based on the type as described in the following sections.
If you are creating additional hardware asset types, such as desktop and laptop entries, the best practice is to create them as children of the Computer type. There are certain functions that are only available to assets of type Computer and to its subtypes; for example:
automatic linking of CIs to assets based on serial number, see Hardware asset and computer CI linking
the calculation of software licensing because it looks for hardware assets that are linked to Windows Computers with software items (installed software)
There are also additional internal behaviors and optimizations that make use of the type Computer.
Currently there is a workflow that ensures you are applying the correct life cycle status to an object. For example, you cannot install an asset that is disposed. This workflow will not recognize custom life cycle states or children added to existing states. If you create new life cycle states, then you may be permitting incorrect custom states to be applied to an asset.
If you need to import csv files into Service Manager for use with the IT Asset Management Pack, observe the following rules for your newly created list values:
When a new value has been added to a list, such as adding the Server as a new hardware asset type, the ENUM should be identical to that of the existing values.