ITAM Application Deployment

tip

Role required: admin

To deploy the ITAM application, complete the following steps:

1. Install the ITAM application.
2. (optional) Deploy demo data.

To install the ITAM application for the first time, use the full version pack. To update the application from the previous versions, use the update packages.

Full version deployment

caution

Ensure you are going to install the ITAM application 1.4.2 on the platform version 1.25.0 or later.

1. Install the [ITAM] 1.4.2 full.sop package.
2. In the Simple Application, add a new column Corresponding asset (corresponding_asset_id) to the form view of the Configuration Item (sys_cmdb_ci) table to ensure proper visualization of the relationship between the asset and the current configuration item.
3. If the ITSM application is installed on your instance and you require communication between these applications, install the [ITAM]_ITAM_1_3_1_ITSM_1_12_1_full.sop package and configure the ITAM-ITSM Connector. Once configured, you do not need to reconfigure it as it remains actual for further updates.

Update installing

Install all versions and patches in their release order.

Example:

To update the application from version 1.1.1 to 1.4.2, sequentially install the update packages in the following order: 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.4.0, 1.4.1 and 1.4.2. Always follow the version deployment instructions.

1.4.2

Update version 1.4.1 to version 1.4.2

1. Install the [ITAM] 1.4.2.sop package.
2. In the Simple Application, add a new column Corresponding asset (corresponding_asset_id) to the form view of the Configuration Item (sys_cmdb_ci) table to ensure proper visualization of the relationship between the asset and the current configuration item.
3. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

Clear related asset lists in the canceled inventory tasks

In this release, we fixed an issue that caused assets added to an inventory task to remain related to it after the task was moved to the Canceled state if at least one Inventory report had been added to the task. Those assets were unavailable for adding to other ITAM tasks and Demands.

When upgrading to version 1.4.2, ensure that no assets in your instance are still related to inventory tasks that have already been canceled. To do so, do the following:

1. Open the list view of the Asset - Task (itam_m2m_task_asset) table with the /list/itam_m2m_task_asset?condition=(task_id.sys_db_table_id%3D168669266704175184%5Etask_id.state%3Dcompleted%5Etask_id.closure_code%3Dcanceled) filter.

   • If the list is empty, no further actions are needed.

2. If the list contains records, execute the server script To remove assets from canceled inventory by the {your instance URL}/record/sys_script/174557113618984162 link. The script will remove the related asset records from the canceled Inventory Tasks, and they will become available for tasks and demands.

3. Reopen the list from step 1 after a short time (the exact time depends on the current system workload and the number of assets to be removed). The number of records in the Asset - Task (itam_m2m_task_asset) table with the filter from step 1 will gradually decrease until the list is empty. The assets removed from canceled inventory tasks will become available for demands and other ITAM tasks.

1.4.1

Update version 1.4.0 to version 1.4.1

1. Install the [ITAM] 1.4.1.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

1.4.0

Update version 1.3.3 to version 1.4.0

1. Install the [ITAM] 1.4.0.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

Company owner field in the asset form

A new mandatory field Owner company is added into the asset form in the ITAM version 1.4.0. Execute the Update assets - set owner company scheduled script to populate this field with the reference to the company owning the stock that the asset is related to.

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record Update assets - set owner company ({your instance URL}/record/sys_schedule_script/173945677010361671) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight. Example: 2024-11-28 01:02:00 The system will run the script according to the timezone set in the Preferences menu of the platform, not the timezone set on your device. edit the timezone in the Preferences so that it matches the timezone on your device. If they differ, for your convenience, edit the timezone in the Preferences so that it matches the timezone on your device.

When the script is executed, in the active records, the Owner company (company_id) field is completed with the Stock.Company owner (stock_id.consumer_id) field value.

Company owner field in the asset registration task

Besides, the mandatory Owner company field is added to the asset registration task form. Execute the Set registration tasks owner company scheduled script to complete the field of the tasks that are not in the Canceled state with the reference to the company owning the stock the asset is related to.

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record Set registration tasks owner company ({your instance URL}/record/sys_schedule_script/173884402615726716) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight. Example: 2024-11-28 01:02:00 The system will run the script according to the timezone set in the Preferences menu of the platform, not the timezone set on your device. edit the timezone in the Preferences so that it matches the timezone on your device. If they differ, for your convenience, edit the timezone in the Preferences so that it matches the timezone on your device.

When the script is executed, all registration tasks that are not in the Canceled state, the Owner company (owner_company_id) field is completed with the value of the Stock.Company owner (stock_id.consumer_id) field value.

1.3.3

Update version 1.3.2 to version 1.3.3

caution

Before installing ITAM 1.3.3, ensure you have installed platform 1.25.0 or a later version.

In this version of the application, the logic of the Documents and Asset Contracts fields has been updated. It is now also possible to create asset records from the configuration items according to specified conditions. To correctly upgrade ITAM to version 1.3.3, follow the instructions below:

1. If you applied the solution for restoring Asset Contract functionality on the platform version 1.25.0 when you first installed version 1.3.2, or when you upgraded ITAM to version 1.3.2, make a rollback of those changes.
2. Install the [ITAM] 1.3.3.sop package.
3. (optional) Install the ITAM-ITSM Connector and configure the forms if not done previously.

Update Asset Contracts records

In Asset Contracts, the Currency, Customer, and Consumer fields are now aligned with the same fields in platform version 1.25.0. To update the existing records on your instance, execute the Update itam contracts script:

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record Update itam contracts ({your instance URL}/record/sys_schedule_script/173650151815017134) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight. Example: 2024-11-28 01:02:00 The system will run the script according to the timezone set in the Preferences menu of the platform, not the timezone set on your device. If they differ, for your convenience, edit the timezone in the Preferences so that it matches the timezone on your device.

   After the Update itam contracts scheduled script is executed, the following changes will occur in the existing asset contracts: the Category field will be filled with the data migrated from the disabled Contract category field, the mandatory Currency field will be filled with the currency specified in the currency.default system property. Also, in active asset contract documents, the Subtype field will be filled with the value of the related Asset Contract category.

3. Click Save or Save and exit to apply the changes.

Update existing records in the Documents table

In the Documents form, the Subtype field has been updated to receive the value of the related Asset Contract category. To update the document record data on your instance, follow these steps:

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record Set document subtype ({your instance URL}/record/sys_schedule_script/173712103517910376) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight, but 1 hour later than the run time of the Update itam contracts scheduled script. Example: 2024-11-28 01:02:00 The system will run the script according to the timezone set in the Preferences menu of the platform, not the timezone set on your device. If they differ, for your convenience, edit the timezone in the Preferences so that it matches the timezone on your device.

3. Click Save or Save and exit to apply the changes.

After the Set document subtype scheduled script is executed, in the forms of the inactive documents of type Contract, the field Subtype is filled with the value of the corresponding contract category.

Create asset records from configuration items

In this version, if necessary, you can activate asset record creation together with creating configuration items and asset records creation from the configuration items that already exist in the system. Read more about activating and configuring this functionality in the Asset Registration with CI article.

Add serial numbers to the CIs from the corresponding asset records

If required, you can fill the Serial number fields of the configuration items with the value of the Serial number field of their corresponding assets. To do so, execute the scheduled script Set CI serial number from Asset. This script will add the serial numbers of the corresponding assets to the records of the configuration items.

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record Set CI serial number from Asset ({your instance URL}/record/sys_schedule_script/173451471416090603) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight. Example: 2024-11-28 01:02:00 The system will run the script according to the timezone set in the Preferences menu of the platform, not the timezone set on your device. If they differ, for your convenience, edit the timezone in the Preferences so that it matches the timezone on your device.

3. Click Save or Save and exit to apply the changes.

1.3.2

Update version 1.3.1 to version 1.3.2

caution

Before installing ITAM 1.3.2, ensure you have installed platform 1.23.3 or a later version.

If you have the ITAM application 1.3.2 or lower versions installed and you update the platform to version 1.25.0, the asset contract functionality will be limited.

Restore the functionality of the Asset Contracts for ITAM 1.3.2

1. In the agent interface, go to Preferences → Admin Preferences.
2. In the Application field, select Simple.
3. Select or create a new local pack and set it current.
4. Open the Contract category (contract_category) column record of the Contract (contract) table.
5. Select the Active checkbox.
6. Click Save or Save and exit to apply the changes.
7. Open the Currency (currency_id) column record of the Contract (contract) table.
8. In the Column override related list, click New.
9. In the form that opens, specify the Asset Contract (itam_contract) in the Table field for the Currency field.
10. Select the Mandatory Override checkbox.
11. Ensure the Mandatory checkbox is cleared.
12. Click Save or Save and exit to apply the changes.
13. (optional) Complete the new local pack. To do so:
    1. Navigate to Configuration → Local Packs and open the local pack record you created earlier.
    2. Specify Completed in the State field.
    3. Click Save or Save and exit to apply the changes.

1. Install the [ITAM] 1.3.2.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

1.3.1

Update version 1.3.0 to version 1.3.1

1. Install the [ITAM] 1.3.1.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

1.3.0

Update version 1.2.5 to version 1.3.0

caution

Before installing ITAM 1.3.0, ensure you have installed platform 1.23.3 or a later version.

1. Install the [ITAM] 1.3.0.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure forms if not done earlier.

Update asset names

ITAM version 1.3.0 introduces a more concise asset naming format.

Previous format	Format introduced with ITAM 1.3.0
A00008531 Server equipment Application server DELL PowerEdge T40	A00008531 Application server DELL PowerEdge T40

To update the names of the assets created in the previous ITAM versions, run the scheduled script [ITAM] Change name assets. To do so, follow the instructions below:

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record [ITAM] Change name assets (/record/sys_schedule_script/172787324211246773) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight. Example: 2024-11-28 01:01:00 The system will run the script according to the time, set in the Preferences menu of the platform, not the time set on your device. If they differ, for your convenience, edit the time zone in the Preferences so that it coincided with the time on your device.

3. Click Save or Save and exit to apply the changes.

Add closure codes to the completed registration tasks

In ITAM 1.3.0 we added closure codes to the registration tasks.

To add the closure codes to the registration tasks that were completed before installing ITAM 1.3.0, run the scheduled script [ITAM] Add closure code to already completed assets registration tasks. To do so, complete the following instructions:

1. Navigate to System Scheduler → Scheduled Scripts.

2. Open the record [ITAM] Add closure code to already completed assets registration tasks (/record/sys_schedule_script/172985946514168137) and complete the fields with the following values:

   Field	Value
   Active	Yes
   Run frequency	Once
   Run date and time	Specify the time when the system load is minimal, for example, after midnight. Example: 2024-11-28 01:02:00 The system will run the script according to the time, set in the Preferences menu of the platform, not the time set on your device. If they differ, for your convenience, edit the time zone in the Preferences so that it coincides with the time on your device.

3. Click Save or Save and exit to apply the changes.

1.2.5

Update version 1.2.4 to version 1.2.5

1. Install the [ITAM] 1.2.5.sop package.
2. Update the ITAM-ITSM connector with the [ITAM]_ITAM.1.2.5_ITSM.1.12.1.sop package, if the ITSM application and this connector have already been installed on your instance.
3. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

Add full text search for assets on the portal

This version has a full text search for assets in the asset list on the portal. For this functionality to work, from this version all assets get a search index.

To add indices to the existing assets, run the [ITAM] Reindex Assets table server script. To do so, complete the following steps:

1. Navigate to System Settings → Server Scripts.
2. Open the record [ITAM] Reindex Assets table (/record/sys_script/172010221518000015)
3. Click Run.

1.2.4

Update version 1.2.3 to version 1.2.4

1. Install the [ITAM] 1.2.4.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure forms if not done earlier.

This patch introduces two updates: a status model for nomenclatures that prevents asset registrations for outdated nomenclatures, and an updated parent-child asset relationship logic. If nomenclature and asset records already exist on your instance, you must run the appropriate scripts to update this data after installing the update package.

Add nomenclature state

note

Follow the instruction below if the Nomenclature (itam_nomenclature) table contains records.

Run the scheduled script Set nomenclature state to set Active state for existing nomenclature records. To do so, follow the instructions below:

1. Navigate to System Scheduler → Scheduled scripts and open the record Set nomenclature state (record/sys_schedule_script/171698291418285351).
2. Select On Demand in the Run frequency field.
3. Click Run.

Create one level "parent asset – child asset" relationship

note

Follow the instruction below if the Assets (itam_asset) table contains records.

When updating your application, you can run the script that cuts multi-level child-parent relationships and leaves only the child-parent pairs on the first level. Child assets will repeat the stage and state of their parent asset. Child assets of other levels will remain related to the parent assets, but they will not repeat their stage and state.

According to the logic of ITAM version 1.2.4 and higher, parent assets can only have child assets on the first level. The child asset cannot be a parent for another asset. Setting multi-level parent asset – child asset relationships will be unavailable.

To set a one level relationship between the assets, run the Set relation between Parent and Child assets scheduled script.

If there are no asset records that are related as a parent and child, you do not need to run the script as the new algorithm creating one level asset relations will be applied automatically.

1.2.3

Update version 1.2.2 to version 1.2.3

1. Install the [ITAM] 1.2.3.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

With this release, a problem has been resolved that resulted in the script not being able to set REM attribute values for configuration units. To update the REM attribute values of existing configuration units related to assets, run the scheduled script Set re model in CI as described below. If there are no asset records yet, you do not need to run the script.

caution

Follow the instruction below only if the Assets (itam_asset) table contains records.

1. Open the scheduled script record Set re model in CI (record/sys_schedule_script/171560985413106860).
2. Select Once in the Run frequency field.
3. Select the Active checkbox and specify the Run date and time as an integer of minutes in the future.
4. Click Save.
5. To monitor the script execution, follow the records in the Main Logs (sys_log) table.

As a result, the configuration items of the REM attributes related to existing assets will be updated.

1.2.2

Update version 1.2.1 to version 1.2.2

1. Install the [ITAM] 1.2.2.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure the forms if not done earlier.

In this version, a new field Active appeared in the Asset (itam_asset) table. Run the scheduled script Set Active in existing Assets to set its value for all asset records that already exist on your instance.

caution

Follow the instruction below if the Assets (itam_asset) table contains records.

1. Open the scheduled script record Set Active in existing Assets (record/sys_schedule_script/170965537611177121).
2. Select Once in the Run frequency field.
3. Select the Active checkbox and specify the Run date and time as an integer of minutes in the future.
4. Click Save.
5. To monitor the script execution, follow the records in the Main Logs (sys_log) table.

When the script is executed, the Active field on the asset record forms is filled in with the values Yes or No depending on whether the asset is in the final state and stage.

1.2.1

Update version 1.1.1 to version 1.2.1

1. Install the [ITAM] 1.2.1.sop package.
2. (optional) Install the ITAM-ITSM Connector and configure forms if not done earlier.