---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Create a CI manually

# Create a CI manually in Service Graph Workspace {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read

Create a CI in Service Graph Workspace, while applying Identification and Reconciliation Engine (IRE) processes and other requirements for the CI's class. IRE identification rules enforce the new CI to be unique and to comply
with other class requirements.

## About this task

Creating specialty CIs such as a service instance, isn't supported in this Create CI experience. Typically, such CIs aren't discoverable and you must create them manually using specific wizards, such as the [Application service(Service instance) wizard](https://www.servicenow.com/docs/LKd87HjvwYKREPw7DmJc5Q "Create an application service to adhere to Common Service Data Model standards and to standardize the organization, maintenance, and monitoring of services in your organization.").  
You can access the Create CI experience in either of the following ways:

* Select the Create CI link in the Management tools, Create section on the Governance view of Service Graph Workspace which lets you then select a class for the new CI.
* Drill down a class group bar in the CI Summary tab on the CI overview tile, in which case the class you are drilling down from becomes the class for the new CI. This option is available only if you drill down a class that isn't excluded for the Create CI experience. For information about excluding classes for the Create CI experience in Service Graph Workspace, see [Limit the class list for new CIs created in a workspace](https://www.servicenow.com/docs/V~R757GfDnysfEBwGQqjgg "Limit the selection of classes for a new CI being manually created in your workspace, to only those classes that are relevant to that workspace. When then creating a new CI in the respective workspace, users can only select a class that is authorized as an option.").
{#create-ci-manual-sg-workspace__ul_efr_t4n_52c}

As you progress through the procedure, fields appear dynamically according to your selections and entries on the current or previous pages.  
To manually create a new CI without applying IRE processes (Core UI), see [Populating the CMDB](https://www.servicenow.com/docs/RFEkBbd3mAJUu78e4wYSRA "You can populate the CMDB by using Discovery, by using the IntegrationHub ETL or Import Sets to import and integrate data from a third-party source, by integrating with an external CMDB, or by manually creating CIs."). For more information about mandatory attributes, IRE processes, dependent CIs, and the CI relationship editor (Core UI), see:

* [Set a CI attribute to be mandatory](https://www.servicenow.com/docs/~dOsIFHZybrseBZals52bQ "Configure a CI attribute as mandatory so it is included in the CMDB Health tests for the required metric if enabled. Required is a metric of the CMDB Health completeness KPI.")
* [Identification rules](https://www.servicenow.com/docs/qG5r~lgjzB8eUVVTvbX_fw "The CMDB identification process relies on identification rules to uniquely identify CIs.")
* [CMDB classifications and class dependency](https://www.servicenow.com/docs/Hbp9Nnl3Ji4nqSA2NkFi0w "CMDB classifications are groups of CIs that share attributes and are stored in their own class table. Classifications let administrators to define a class hierarchy for the CIs within the CMDB.")
* [CI relationship editor](https://www.servicenow.com/docs/aLIVU03XrvYytnPTnLciqQ "Use the relationship editor to view, create, modify, or delete CI relationships. Open the relationship editor from the CI Relations formatter.")
{#create-ci-manual-sg-workspace__ul_q3s_hhy_4dc}

## Before you begin

Configure any customizations to the create CI experience before creating new CIs:

* Complete any request by an administrator for additional non-mandatory attributes. For information about how an administrator can use configuration identifiers to incorporate requests for attributes into the flow of creating a new CI, see [Request additional attributes for new CIs](https://www.servicenow.com/docs/~OvRPivee9RqCciQRAxBeQ "Integrate a request for specific CI attributes when manually creating a new CI in your workspace. Then, when creating a new CI in the respective workspace, users can enter values for the requested attributes, as appropriate for the new CI.").
* Complete any settings for limiting the list of classes available to choose from, for a new CI. For information about how an administrator can use configuration identifiers to create a custom list of classes for a new CI, see [Limit the class list for new CIs created in a workspace](https://www.servicenow.com/docs/V~R757GfDnysfEBwGQqjgg "Limit the selection of classes for a new CI being manually created in your workspace, to only those classes that are relevant to that workspace. When then creating a new CI in the respective workspace, users can only select a class that is authorized as an option.").
{#create-ci-manual-sg-workspace__ul_s21_m4w_zdc}  
If you want additional actions to be performed after creating a CI, such as creating a record that references the new CI, implement the ManualCreateCIExtPoint extension point:

* In the getAppId() function, add the sys_id of the application containing the workspace from the UX Application \[sys_ux_page_registry\] table.
* In the postInsertCI() function, define the additional actions you want to perform.

{#create-ci-manual-sg-workspace__ul_drs_xfn_tfc}Your extension point implementation runs after a new CI is created in the application specified in getAppId(). You can create additional implementations as needed for additional applications. For more information about extension points, see [Using extension points to extend application functionality](https://www.servicenow.com/docs/access?context=extension-points&version=australia&pubname=australia-api-reference&ft:locale=en-US).

Role required: cmdb_manual_ci_ire_access (contained in the sn_cmdb_editor role by default)

## Procedure

1. Navigate to WorkspacesService Graph Workspace.
2. On the Governance view of Service Graph Workspace, use one of the following options:  
   * Select the Create CI link, and then:
     1. On the Select class page, select the class for the new CI from the Class drop-down list. Classes without a valid identification rule are grayed out in the list and you can't select them.
     2. Select Continue.
     {#create-ci-manual-sg-workspace__ol_blc_5rn_52c}
   * On the CI overview tile, select the CI Summary tab, and then:
     1. Select the group bar with the class that you want to create the new CI in.
     2. Scroll down to the list view for the class group, and select the class in which you want to create the new CI.
     3. On the class list view page, select the Create CI button.  
        Note:  
        If you selected a class that is excluded from the Create CI experience, the New button appears. Select New to manually create a new CI without applying IRE processes (Core UI).
     {#create-ci-manual-sg-workspace__ol_hvx_5sn_52c}
   {#create-ci-manual-sg-workspace__ul_frn_4rn_52c}

   Continue to fill out the rest of the Create a new CI pages as described in the following steps.
3. Required attributes:  
   Configure attributes that are either mandatory for the new CI's class, or which the identification rule for the new CI's class requires. Also, if the new CI is a dependent CI, configure the dependency relationship.
   * In the Dependent-upon CI section, select a CI that the new CI depends on.

     Dependent-upon class: Select the class of the dependent-upon CI.

     Dependent-upon CI: Select the search icon and in the Dependent-upon CI dialog box, select a CI by selecting its link in the Name column.
   * In the Identifier entries section, select criterion attributes and set their values to uniquely identify the CI.

     Criterion attributes: In the drop-down list, select one or more criterion attributes sets. This drop-down list omits criterion attributes that are based on the Product instance identifier attribute.
   * In the criterion attribute fields section scroll down the page if needed and enter values for the criterion attributes fields for the CI.

   {#create-ci-manual-sg-workspace__ul_tdc_zkg_pdc}

   Select Continue. If the new CI is detected as a duplicate of an existing CI, then the CI already exists dialog box appears. Select Review existing CI and then decide
   whether to change the existing or the new CI to prevent the duplication and to continue creating the CI.
4. Additional attributes:  
   Enter values for attributes, such as Operational status, that your administrator is requesting in addition to the required attributes from previous pages.

   Select Continue.
5. Relationship definition:  
   Review any existing relationships and decide whether to add a relationship for the new CI. For dependent CIs, a dependent relationship was already created in an earlier step.
   1. Select Add.
   2. On the Add relationships page, select a Relationship type.

      The Parent/Child notations in each relationship type denotes whether the new CI will have the role of a child or a parent in the new relationship.
   3. In the Configuration Item list, select the CIs that the new CI will have the relationship with. Whichever parent/child role you selected for the new CI, the selected CIs will have the other role.
   4. Select Add.

   {#create-ci-manual-sg-workspace__ol_tlt_w4b_qdc}  
   Note:  
   Creating relationships to the User and the Group tables is supported, however, those relationships aren't processed by IRE.

   On the Relationship definition page, select Continue.
6. Review:  
   Review all the details of the new CI. Select Create to approve and create the new CI, or Back to change definitions.
7. In the New CI created dialog box, select Done to exit the operation, Review new CI to open the form view for the new CI, or Create another CI.
{#create-ci-manual-sg-workspace__steps_epg_bs2_pdc}

## Result

In the new CI, Discovery source is set to Manual via IRE.

## What to do next

You can view the new CI or other CIs, using CI Form in Service Graph Workspace. For more information about using the CI Form, see [Manage CI details using CI Form in Service Graph Workspace](https://www.servicenow.com/docs/q17qE_pLihaDdtEVUHxC3g "Use CI Form in Service Graph Workspace or in another workspace, to view, edit, and manage details of a CI such as its attributes, related lists, and CMDB 360 records. When updating CIs, IRE rules are applied to avoid potential issues such as duplicate CIs. CI Form supports derivation of form configurations throughout the CMDB hierarchy.").

*[\>]: and then