Revise a configuration item using design and assign

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 2 minutes de lecture

    • Revise a CI (Configuration Item) of the connection to update a CI in the Telecommunications Network Inventory application.

    Avant de commencer

    Role required: sn_ni_core.inventory_admin

    Procédure

    1. Navigate to Workspaces > Network Inventory Workspace.
    2. Select the list icon (List icon.), and then go to Changes > All.
    3. Select the desired change request.
      To create a change request, see Create a change request from Network Inventory Workspace.
    4. Select the Change Tasks tab.
    5. Select New.
    6. Choose a change task type:
      • Planning
      • Implementation
      • Testing
      • Review
    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.
    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.
      Remarque :
      • 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.
    12. Facultatif : 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.
      • 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.

    Que faire ensuite

    You can update the cloned CI and operationalize the CIs. To learn more about operationalization, see Operationalize a configuration item.