---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Capture affected CI information

# Capture information on affected configuration items in an incident {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Capture information on affected configuration items (CIs), with type as asset, in an
incident to keep a record of the updated, repaired, swapped, or retired configuration
items.

## Before you begin

Role required: itil or admin

Activate the Hardware Asset Management Professional plugin (com.sn_hamp).

## About this task

You can tell where the assets are located, by keeping track of the assets, how they
are used, and when changes were made to them. This information helps you to monitor
and manage the assets in your company using a systematic approach.

If you are not the caller of the incident and have a CI value in the affected CIs
list, it is mandatory to provide information on the CI before changing the state of
the incident to Resolved.  
You can enter CI information either from the Affected CIs related list or from the form layout of the Affected CIs. You need to manually add the Asset Action and the Swapped CI fields in the related list. {#track-ci__table_uz4_lzw_clb__entry__2}

| Where | How |
|-|-|
| Related list | * In the Affected CIs related list, click the settings icon ![Personalize list](). * Move the Asset Action and the Swapped CI fields from the Available column to the Selected column. * Click OK. {#track-ci__ul_wvp_h1x_clb} |
[Table 1. Add fields in the related list]

{#track-ci__table_uz4_lzw_clb}  
Note:  
The CI value is updated only if the incident state is updated to Resolved by any user excluding the caller. The CI value is not updated if:

* The incident state is updated as Resolved by the caller even if the Asset Action is populated.
* The incident is directly moved to Closed state.
{#track-ci__ul_nsl_kyx_gtb}

## Procedure

1. Navigate to AllIncidentOpen.  
   Note:  
   If the UI16 module link redirection feature is enabled in Service Operations Workspace (SOW) and the UI16 module supports the redirect configuration, navigating through UI16 paths automatically redirects you to the equivalent list or record pages in SOW instead of displaying the UI16 forms or lists. For more information, see [Redirect UI16 module links to Service Operations Workspace](https://servicenow-prod.fluidtopics.net/vL8HZs36~TCAlAHAiJ5i~w "Redirect classic UI16 module navigation links to the equivalent Service Operations Workspace (SOW) experience.").
2. Open an incident.
3. Navigate to the Affected CIs related list before resolving the incident.
4. **Optional:** If you want to enter information in the form layout, click the CI.
5. On the related list or the form, fill in the fields.  
   {#track-ci__table_prw_kpt_blb__entry__2}

   | Field | Description |
   |-|-|
   | Asset Action | Information on whether a CI is updated or repaired, swapped with another CI, or retired from the system. The options available are: No action, Update/Repair, Swap, and Retire. Note: If you swap or retire a CI, the sn_hamp_asset.swap or sn_hamp_asset.retire events are generated respectively. |
   | Swapped CI | Information on the new CI that is swapped with the existing CI. Note: * This field appears only when you select the value of the Asset Action field as Swap. * The CI values available for swapped CI are the ones with asset CI class as hardware. * The Swapped CI is assigned to the Caller. If the Caller is an Asset Manager, they have the option to reassign it to the appropriate user. {#track-ci__ul_wp2_xgc_dlb} |
   [Table 2. Information on Affected CIs]

   {#track-ci__table_prw_kpt_blb}
6. Click Update.  
   The record is saved and the information about CI is stored in the \[task_ci\] table.  
   Note:  
   You can filter the Affected CIs related list to have the list of affected CIs with class as Asset.

*[\>]: and then