Skip to main content
Version: 1.2.5

Patch 1.2.3

This update includes improvements and fixes optimizing ITAM logic and enhancing data security. This product version also provides a simplified procedure for allocating pieces of consignment assets without a mandatory approval.

Improvements​

Validation of assets queued for addition

Assets are now excluded from task A during the validation process if:

  • they were added to task B before they were added to task A.
  • they no longer meet the task conditions or there is a discrepancy among certain fields in the asset record and the fields in the task.

Asset allocation of consignment pieces without approval

Now, if an allocation task includes only consignment consumptions, the task can be completed without prior approval. Whereas the tasks that include not only consignment consumptions, but also single assets still require approval before completion.

Documentation

The content of articles has become more uniform, logical, and easier to read. In this respect, we have improved the navigation in the side menu, added missing information, expanded the description of fields and UI actions on the forms, and brought them all to a standard view.

Fixes​

DEF0019045: It was impossible to set REM attribute values ​​for configuration items using a script. Now REM attributes of configuration items in this case are updated correctly. To update the REM attribute values ​​of existing configuration items related to assets, run the scheduled script Set re model in CI.

DEF0019004: In the past versions, selecting the Not Found checkbox on the form of an asset in an inventory or decommissioning task caused the value in the Asset is in the task technical field to change to No, but, in fact, the asset still remained in tasks of the mentioned types. Now, selecting the Not Found checkbox does not change the value of this attribute if the asset is an active inventory or decommissioning task.

DEF0018803: The maintenance and upgrading task forms after the allocation and return of a replacement asset had erroneous behaviour. In the previous versions, after allocating a replacement asset, the Replacement asset field was not displayed on the forms of the mentioned tasks and the Allocate replacement button remained available. Now, after allocating a replacement asset to a user, the button disappears, and the Replacement asset field appears on the form showing a relevant value. Also, the system behavior after returning a replacement asset is fixed. Previously, the Replacement asset field and the Return replacement button did not disappear from the task form. Now, after returning the replacement asset, the button disappears and the Replacement asset field is hidden from the task form.

DEF0018767: Previously, when creating a new item record, the Category field was automatically filled in with a specific value after selecting the Spare parts kit checkbox. Now selecting this checkbox does not entail changes in the Category field. Thus, the category of spare parts and accessories can be any in accordance with the company’s accounting process.

DEF0018706: There were some lapses of access control rules that could affect data security. For this purpose, we unified the access rules for reading records of ITAM tables described below. Now reading records of these tables is available to users with the admin or itam_agent role. Creating, deleting, and editing entries in these tables is prohibited for all other users.

Tables:

  • Asset – Task
  • Asset – Document
  • Document – Task
  • Asset counters
  • Asset Updates
  • Consumption Updates
  • Consumptions (itam_consumption) – read access has been configured for this table for users with the admin or itam_agent role. The access criteria for creating and editing records in this table have not changed as they remain relevant and differ from the requirements in this defect.
  • Create relation between assets and tasks
  • Delete relation between assets and tasks
  • Asset Creation Errors
  • File of registration assets
  • Inventory Histories
  • Inventory Reports
  • Nomenclature - added an access control rule for this table to prohibit deleting records for users with the roles itam_agent and admin.

DEF0018513: The system behaved incorrectly on asset forms related to selecting the Unfixable checkbox. Previously, selecting the Unfixable checkbox on an asset form caused the automatic creation of a decommissioning task, however the value in the Asset is in the task technical field remained No. Now, after selecting the Unfixable checkbox and automatic creation of a decommissioning task, the value in the Asset is in the task field changes to Yes. Also, previously, when completing a repair task if the asset was pronounced beyond repair (the value Unfixable was selected), a message appeared indicating that this asset had already been added to another task. Now, the message appears only after a repair task is completed with the closing code Unfixable meaning that a decommissioning task has been created for the asset.