Version 1.8.0
In this version, we expanded the configuration capabilities of the Tasks, AMDB, and Purchase Requests modules, streamlining asset management workflows. You can now conduct inventory tasks by specific locations and use barcode scanners for stock inventory.
Previously, attaching documents for task approval and completing was mandatory, which did not fit all scenarios. We removed this restriction, allowing administrators to define whether document attachments are required for each task type.
Working with assets is now more flexible: system administrators can enable management of the Spare parts kit checkbox on individual assets regardless of nomenclature settings; bulk verification of asset records created from configuration items accelerates their registration; and total asset costs are automatically calculated in the default currency.
Additionally, management of direct purchases is more efficient, as you can now include demand items with nomenclatures linked to different providers in a single purchase request.
This update also includes UI improvements and fixes for more stable system operation.
New features
Location-based inventory
You can now conduct asset inventory at selected locations rather than only at individual stocks. To support this, we added a new task type: Location Inventory. Assets are included in the inventory report if they are found in one of the specified locations. The rest of the mechanism works as usual.
For more information, see Location Inventory.
Stock inventory using a barcode scanner
In this version, we expanded the list of inventory methods with support for barcode scanners. The system supports scanners paired with a computer or a mobile device. When using a mobile device, pay special attention to pairing configuration, as differences in language settings and barcode character language can cause scanning errors.
In the itam.barcode_scanner.separators system property, specify the separators the scanner uses between scanned asset values. In future versions, this property will also apply to location inventory tasks.
For more information, see Stock Inventory.
Bulk validation of asset records requiring verification
You can now select all required asset records that are in the Pending verification state and were created from configuration items to complete their registration in the system with a single action.
For more information, see Registering Asset Records from Configuration Items.
Improvements
Automatic calculation of total costs on the asset form
We added a mechanism that calculates and populates the Total cost field on asset forms. The value is shown in the currency selected as the default in the currency.default system property. The currency code is also displayed in the Default currency field.
For more information, see Asset.
Ability to manage the "Spare parts kit" attribute on an asset record independently of its nomenclature
ITAM administrators can change the Spares parts kit checkbox on an asset form regardless of the Spare parts kit value of its nomenclature, provided that the asset is not currently involved in any active task. They can also specify the required Spare parts kit value in the asset registration file.
This feature is available only when the itam.asset.spare_parts_kit_change.enabled system property is enabled. By default, the property is set to false.
For more information, see Asset.
Flexible selection of demand items in a purchase request
Now, by default, you can add demand items linked to any nomenclatures to the purchase requests that have the direct purchase method. So you can create a purchase request with the required set of demand items regardless of their relation to the provider specified in the request.
To match providers in purchase requests with the providers in the demand item nomenclatures, set the new itam.purchase.nomenclature_providers.ignore system property to false.
For more information, see Purchase Request.
Making ITAM task documents optional or required
ITAM administrators can now define which tasks require document attachments for approval and completion. When document attachments are not mandatory, users can still attach related documents.
Define whether document attachment is required in the following system properties.
Closing documents in tasks:
- Registration: itam.registration_assets.documents_mandatory.enable
- Allocation: itam.asset_allocation.documents_mandatory.enable
- Return to Stock: itam.asset_return.documents_mandatory.enable
- Maintenance: itam.asset_maintenance.documents_mandatory.enable
- Upgrading: itam.asset_upgrading.documents_mandatory.enable
- Relocation: itam.asset_relocation.documents_mandatory.enable
- New Responsible: itam.new_responsible.documents_mandatory.enable
- Stock Change: itam.stock_change.documents_mandatory.enable
- Decommissioning: itam.asset_depreciation.documents_mandatory.enable
- Disposal: itam.disposal.documents_mandatory.enable
- Transfer: itam.asset_transfer.documents_mandatory.enable
Non-warranty service documents in a task:
- Maintenance: itam.asset_maintenance.non_warranty_contract_mandatory.enable
For more information, see System Properties.
Expansion of the "itam_nomenclature_manager" role
The itam_nomenclature_manager role now includes permissions to update the following tables:
- Nomenclature Provider (itam_m2m_nomenclature_provider): create and update.
- Actual Cost Item (itam_actual_cost_item): create, update, and delete. Editing and deletion are possible only in the Unallocated state.
For more information, see Role Model.
Endpoint response code updates
| Response code | Response (new) | Response (previous) |
|---|---|---|
| 200 | The consignment quantity has been successfully updated: The request was processed correctly. | The asset has been successfully scanned |
| New: 201 | The asset has been successfully scanned: The request was submitted correctly. The asset has been recorded in the inventory statement. | - |
| 422 |
| The inventory history has been uploaded |
For more information, see Inventory Methods.
Localization of CMDB entities
The ESM platform version 2.2.0 introduced localization of CMDB entity names into the system languages. In ITAM, you can now select the preferred language for displaying entities in the itam.cmdb.naming.language_code system property. This improves visual consistency and makes the asset hierarchy map easier to analyze and present to customers and other stakeholders.
In addition, the logic for generating the nomenclature and asset record display names has been updated to take into account the new Name field in the CMDB class records.
- If the required entity translation is unavailable, the system automatically switches to English. If English is also unavailable, it switches to the first available language.
- When importing nomenclatures via an XLSX file, the data is matched against the current interface language. Rows with a mismatched language are skipped, and information about the skipped records is logged in the error log.
Demo Data
The updated demo data package supports all updates in version 1.8.0 and includes CMDB translations in Russian, English, and Portuguese. To select the display language, use the itam.cmdb.naming.language_code system property.
The demo data now also includes:
-
the itam_budget_agent role to the ITAM-OPERATIONS group,
-
the ITAM-BUDGET-APPROVERS group with the itam_budget_approver role,
-
the ITAM-BUDGET-MANAGERS group with the itam_budget_manager role,
-
new users:
- Diana Finansova
- Boris Byudzhetov
- Anna Byudzhetova
- Egor Byudzhetov
- Dmitry Byudzhetov-Apruvov
- Arina Byudzhetova-Apruvova
- Tatiana Byudzhetova-Apruvova
For more information, see ITAM Demo Data.
UI Improvements
On the ITAM Demand (itam_demand) and ITAM Purchase Request (itam_purchase_request) table forms, the Remove selected items and Remove demand items buttons have been moved to their respective related lists.
Fixes
DEF0023180: In ITAM tasks and demand item forms, the modal windows for adding assets and demand items displayed incorrectly, making it impossible to select the required records, and clicking the Select all button caused an error. The issue was related to a Platform logic update in version 1.33.0. In this version, the modal window functionality has been restored.
DEF0023038: The introduction of WYSIWYG fields in Platform version 1.34.0 prevented users from performing actions on ITAM contracts because the ITAM Contract table is a child table of the Platform Contract (contract) table. The modal window that appears to confirm an action on an asset contract (cancellation, editing, or termination) required filling in the Work notes field of type WYSIWYG, while the ITAM version 1.7.0 and earlier used the Work notes field of type Text. In this version, the Work notes field in the Asset Contract (itam_contract) table is of type WYSIWYG, which aligns with Platform version 1.34.0 logic.
DEF0022366: In the previous version, we identified an issue where demand items could be canceled from the ITAM Demand (itam_demand) form when two tabs with the same demand record were open simultaneously, and the state in one tab had already been changed to Start delivery while the other had not been updated yet.
A demand item could also be canceled from the related ITAM Demand Item (itam_demand_item) form if it was open at the moment the ITAM Demand state was changed to Start delivery in another tab.
In this version, additional checks have been added to enforce workflow regulations when working with demands and demand lines.