Skip to main content
Version: 1.7.0

Version 1.7.0

In this ITAM release, we introduced tools for processing and importing XLSX files to create and update nomenclatures in bulk. You can also use attribute inheritance within composite asset hierarchies to keep child asset data consistent and reduce manual updates.

You can now track costs for operational tasks related to assets and analyze expenses based on actual data.

You can also include demand items from multiple cost centers in a single purchase request to centralize purchasing and distribute assets across your organization.

New features​

Bulk upload and update of nomenclature records using transformation maps​

You can update the Nomenclature (itam_nomenclature) table in bulk by using configured transformation maps for import. This approach facilitates processing and reduces errors during manual updates of large data sets.

To import new and updated nomenclature records, complete the XLSX template available in the Loading nomenclatures record of the Import Source (sys_import_source) table.

Read more in Nomenclature.

Inheritance of parent asset attributes​

You can now maintain data consistency across asset hierarchies with the automatic transfer of parent asset field values to child assets. The list of inherited fields is defined in the itam.asset.hierarchy_field_inheritance system property.

To ensure stable system behavior, do not reduce the default field list.

After adding new fields to the list, run the scheduled script Inherit values from parent asset to apply changes to the existing assets to update child asset records with the values of the fields added to the system property.

Read more in ITAM System Properties.

Tracking financial costs for ITAM tasks​

You can now create Actual Cost Item records for all ITAM tasks to track expenses related to assets during task execution, such as repairs or maintenance. Information on the related cost items is available in the related lists area on task records.

Read more in Actual Cost Item.

Registering assets without a serial number​

You can register assets without a serial number for specific nomenclatures. You can use it for consumables, consignment assets, and other asset types without serial numbers provided by a manufacturer.

To support this, the Serial number required field is available on the Nomenclature (itam_nomenclature) form with Yes and No choice options. If set to No, the serial number is optional during registration.

If no serial number is provided, the system copies the inventory number into the Serial number field after the asset registration. You can edit this field if you have the admin or itam_admin role.

Read more in Nomenclature and Asset.

Improvements​

Fewer restrictions on stock responsible selection​

You can now select a Responsible for a stock regardless of the company specified as the Stock owner. All active and unblocked users with the itam_responsible role are available for selection.

Purchase requests​

You can manage purchase orders more flexibly with the following updates:

  • Demand items from multiple cost centers

    Previously, you could add demand items from only one cost center to a purchase request. That limitation has been removed.

    You can now include demand items from multiple cost centers in a single purchase request to centralize purchasing and distribute assets across their callers.

  • Specifying the paying company

    The Company field is now available on the purchase request form.

    When you select a Cost center or a Contract, the field is automatically populated based on the first selected record. The remaining related object is then limited to the same company.

New navigation sections​

  • ITAM → ITAM Properites

    You can use the ITAM Properties section to configure application settings and access configuration parameters.

  • ITAM → AMDB → Composite Assets

    The Composite Assets section contains top-level assets that include child assets and are not part of other assets.