Skip to main content
Version: 1.6.0

Version 1.6.0

In this version, we have improved the English localization of the application: we prepared a new package of demonstration data in English with new users, locations, and stocks. We also added the option to generate the inventory report in English and provided a package with English translations of form labels.

In addition to that, we have implemented an option to view full list of child assets included in the current asset across all levels of the relationship hierarchy. We also relocated the buttons to remove assets and сonsignment сonsumptions into the related lists of the ITSM task forms.

New features


Demonstration data in English

Now users can test the ITAM application functionality in English. We have prepared a package of demonstration data in the English language that matches the Russian demo data in structure but contains separate users, locations, stocks, and other records.

To learn more about the contents of the demonstration data package, see the documentation.

Improvements


The list of all assets included in the current asset

We have improved the logic of displaying child assets on the form of the current asset, to provide the accounting specialists with a way to manage information on the complete composition of an asset.

A new button is available in the Child Assets related list that displays the list of all assets that are below the current asset in the relationships hierarchy (both direct child assets and child assets of those assets).

In the formed list:

  • Child assets are grouped by the parent asset.
  • List search and filtering is provided.
  • A new field Level is added that shows the hierarchy level the child asset.

Inventory report in English

To ensure full capability of processing inventory tasks in English, we have added the option to generate and download the inventory report in English. Now, when you click Download report with English selected as your interface language, the document is generated in this language.

English form labels

To improve working with the English localization of the application, we have prepared a package with English translations of all ITAM form labels.

For installation instructions, see the documentation.

New location of buttons

To make processing ITAM tasks more convenient, we have moved the buttons for removing assets, consingment consumptions and spare parts kits from the task forms into the corresponding related lists area.

The following task types were updated:

TaskChange
All task types except maintenance and upgrading
  • The Remove selected assets button is moved from the task form to the Assets related list.
  • The Spare Parts Kits related list was removed from the form. All spare parts kits are now displayed in the general related list of assets.
Allocation task
  • The Remove consignment consumptions button is moved from the task form into the Consignment Consumptions related list.
Maintenance and upgrading tasks
  • The Remove spare parts button is moved from the task form into the Spare Parts Kits related list.
  • The Remove consignment consumptions button is moved from the task form into the Consignment Consumptions related lists.

Fixes


  • DEF0021669: We fixed an issue that prevented opening an explorer window to save a PDF file when a user clicked Download report on the inventory task form. In the new version, the client script of the Manual inventory widget is fixed and the files can be downloaded normally.
  • DEF0021500: We have fixed an issue that prevented the change of user in a consignment consumption added to a maintenance or upgrading task after the task was reassigned. In the new version, we have accounted for the case when the user is changed in the maintenance or upgrading task that was not approved and returned into the Registered state. Now the user of the new asset is automatically specified in the consignment consumption.
  • DEF0020904: We have fixed an issue that caused the ITAM.calculate_employee_assets_location system event to be triggered every time an Employee (employee) record was updated. A necessary condition was added into the corresponding business rule so that the event is now triggered only when the employee's location is changed.