---
sourceDocument: Australia Telecommunications Network Inventory
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/telecom-network-inventory

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecommunications Network Inventory

ft:clusterId :

    - telninv

bundleId :

    - telninv

workflow :

    - Customer and Industry


---

# Revise a configuration item

# Revise a configuration item using design and assign {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Revise a CI (Configuration Item) of the connection to update a CI in the Telecommunications Network Inventory application.

## Before you begin

Role required: sn_ni_core.inventory_admin

## Procedure

1. Navigate to WorkspacesNetwork Inventory Workspace.
2. Select the list icon (![List icon.]()), and then go to ChangesAll.
3. Select the desired change request.  
   To create a change request, see [Create a change request from Network Inventory Workspace](https://servicenow-prod.fluidtopics.net/iJZX~5UTpBLQ~OHJ~tjCMg "Create, review, update, or close a change request for a change model from the network inventory workspace of the Telecommunications Network Inventory application. You can also analyze the instantiation details of the network instance.").
4. Select the Change Tasks tab.
5. Select New.
6. Choose a change task type:  
   * Planning
   * Implementation
   * Testing
   * Review
   {#revise-a-configuration-item__ul_oh4_ymf_fxb}
7. Select Create.  
   A change task form based on the selected change model is displayed.
8. Select Revise CI in the Request type field and fill other fields.  
   To learn more about other fields, see [Change request and change task forms](https://servicenow-prod.fluidtopics.net/7i_oMaHA5XQ1q3y1QnxBtg "The change request forms enable you to request a change.").
9. Select Save.
10. On the Task Attributes form, select a CI from the list of CI to be revised field.
11. Select Submit.  
    A record is created in the Inventory Revision Histories table. The selected CI and related tables are cloned and the cloned CI name is populated in the Configuration item field. Also, both the original and cloned CIs are added under the Affected CIs tab.  
    Note:  
    * To customize the cloning process and the related tables that must be cloned, see ../task/clone-and-revise-a-ci.html.
    * The revision data is automatically archived to the revision history archival rule (Archive Rules → Inventory Revision History Archival Rule\[sn_ni_core_inventory_revision_history\]) table after a period of one year of the CI creation. Subsequently, all data within the archival table is permanently deleted (ar_sn_ni_core_inventory_revision_history) after an additional year. Customization can be achieved by modifying the relevant tables.
    * The revision history currently captures only Configuration Item (CI) attributes, related data, and CI relationships. To include additional data from other tables, logical connection (audit_reference_tableinfo_logical_connection) and physical connection (audit_reference_tableinfo_logical_connection) system properties can be updated. The format for specifying table and column names within these properties is - table1_name:column1_name, table1_name:column2_name.
    {#revise-a-configuration-item__ul_uhx_ftx_pbc}
12. **Optional:** Navigate to a change task and select Validate Revision to validate both original and revised CI.  
    * Before operationalization, you can validate to track the changes performed on the cloned CIs. If the data isn't matching with the original CI, the validation fails and a message is displayed that the cloned CI is updated after the cloning.
    * To customize the validation process, update the Validate CI Revision action flow. To learn more, see [Customize the Validation of Revision CI](https://servicenow-prod.fluidtopics.net/lqVrtsKLXHPLgmWKgYu4ag "Customize the validation process of a CI (Configuration Item) using the Telecommunications Network Inventory application. You can customize the validation process by providing adjustable parameters based on the script.").
    * To skip a field in the validation process, edit (sn_ni_core.revision_val_ignore_fields_logical_connection) table for logical connection CIs and (sn_ni_core.revision_val_ignore_fields_physical_connection) table for physical connection CIs.
    {#revise-a-configuration-item__ul_yvq_bnf_qbc}

## What to do next

You can update the cloned CI and operationalize the CIs. To learn more about operationalization, see [Operationalize a configuration item](https://servicenow-prod.fluidtopics.net/icCEqr2EF8tNbojINwto0g "Operationalize a Configuration Item so that you can finalize the changes and apply them on the original CI.").
**Related concepts**   

* [Revision, operationalization, and decommission of a Configuration Item](https://servicenow-prod.fluidtopics.net/LHxKKB8ArNjYBJL0cmadIg "Revision of Configuration Item (CI) enables you to update the network attributes of a Configuration Item, such as attributes, connection elements, and relations using the Telecommunications Network Inventory application. You can make a safe and efficient update to your network infrastructure by using the CI revision.")

*[\>]: and then