---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Capture affected CI information

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

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Capture information about the asset configuration items (CIs) that are affected by an incident to keep a record of the CIs that are updated, repaired, swapped, or retired.

## Before you begin

Role required: itil or admin

The Hardware Asset Management Professional plugin (com.sn_hamp) must be activated.

## About this task

Tracking assets shows where they're located, how they're used, and when they changed. This information helps you monitor and manage the assets in your organization.

If you aren't the incident caller and the Affected CIs related list contains a CI, provide CI information before changing the incident state 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, select the settings icon ![Personalize list](). * Move the Asset Action and the Swapped CI fields from the Available column to the Selected column. * Select 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 other than the caller. The CI value isn't updated if:

* The incident state is set to Resolved by the caller, even if the Asset Action field is populated.
* The incident is moved directly to the 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://www.servicenow.com/docs/ifUpA_Jb2RQW6HDDErQE2Q "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:** To enter information in the form layout, select 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 Swap is selected from the Asset Action field. * Only CIs with the hardware asset CI class are available to swap. * The swapped CI is assigned to the caller. If the caller is an asset manager, they can 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. Select 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 show only the affected CIs with the Asset class.

*[\>]: and then