--- 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 --- # Define or update a component # Define or update a component {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Define or update a component while working in a changeset. ## Before you begin Important: Starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. Role required: cdm_editor or cdm_admin ## About this task Important: Save your changes whenever you are confident of the changes and before you leave the Config data tab. ## Procedure 1. Follow this procedure to add a component to an application: 1. While working in a changeset, select the more actions icon (![More actions icon.]()) for the components node and select Create component. 2. Enter a unique and meaningful name and then select Create. 2. To perform other actions, select the more actions icon (![More actions icon.]()) for a component and select the action, as follows. | Selection | Action | | Create component | Add a component as described above. | | Create CDI | Add an individual config data item (CDI) and value to the collection. See the instructions in the next step The CDI can have an explicit value, or it can be a variable, override, or overlay. * Variable: The value for this CDI will set the value for an identically-named CDI in an included component. * Override: The value for this CDI will override the value for an identically-named CDI in an included component. You can also override inherited nodes from the child collection. * Overlay: A CDI that does not appear in any included component. {#cdm-component-define__ul_onp_dtq_5pb} | | Include in collections | Include the selected component in specified collections. In the Include in collections dialog box, select the collections that should include the component and then select Include. Note: Only collections that do not already include the component appear in the list. Inclusion of a node takes precedence over inheritance. If a node is both included and inherited, it is instead considered included. | | Add file | Add a file as a file node. You can attach a MIME-type file with a maximum file size of 5 MB. For more information on adding files, see [Manage files using file nodes](https://servicenow-prod.fluidtopics.net/~RZNhiI3wHugd_UlCC_6rQ "Add and manage files using file nodes in the config data model of a CDM app or in a component library."). | | Exclude from inheritance | Removes the inherited node and all child objects from the current collection. You can see excluded nodes in the changeset tree when you access the More actions menu (![More actions icon.]()) and select View excluded data. Excluded nodes are appended with the label "Excluded". Select Include in inheritance from the more actions icon (![More actions icon.]()) to stop excluding the node and re-add it to the changeset. | | Rename | Rename the selected component. | | Delete | Delete the selected component. | | View relationships | View direct relationships with the node. Direct relationships are formed between nodes by inheritance or by being included. | |-|-| {#cdm-component-define__choicetable_hkz_r4h_tpb} 3. Add a CDI: Select the more actions icon (![More actions icon.]()) for the item and select Create CDI. {#cdm-component-define__table_h53_jmt_spb__entry__2} | | | |-|-| | Name | Unique and meaningful name for the CDI. | | Value | Value that the CDI has in the current context or define a variable. * You can specify a direct `key : value` pair. * You can define a variable and specify its default value. Variable definitions have the following form: @@@@: * You can specify a value for a variable using the following form: "": "" * You can specify a contextual variable. These are variables defined out-of-the-box that use the context of the node to set the variable value. The variable uses the following form: "": "(##)" * You can use recursive variables for a CDI value. Recursive variables use other variable values as parameters to set the CDI value. For example, each of these CDI values can resolve the same due to recursive variables: cdi1: @(favorite_food/@(person)@)@ cdi2: @(favorite_food/@(john)@)@ cdi3: waffles {#cdm-component-define__ul_hq3_pp4_kqb} | | Encrypted | Option to specify that the value of the CDI should be encrypted. This option appears only for users with the CDM Secrets \[sn_cdm.cdm_secrets\] role. After you create the CDI, the value appears in all views as `*******`. To view the value on any tab that displays the CDI, users with the CDM Secrets \[sn_cdm.cdm_secrets\] role can select the View encrypted data menu option. | [Table 1. Create CDI] {#cdm-component-define__table_h53_jmt_spb} **Related concepts** * [Viewing and editing config data](https://servicenow-prod.fluidtopics.net/wDuynY3CbIbMdsnLrXip4Q "You can update the config data of an application by creating or opening a changeset on the Config data tab, where you update the structure and CDIs of the config data.") * [How encrypted data is handled](https://servicenow-prod.fluidtopics.net/p_LEFc65xiD27KHPQdknvg "By default, encrypted values appear in all views as *******. Only users with the CDM Secrets [sn_cdm.cdm_secrets] role can view, create, update, and delete encrypted values in config data. The system validates and exports encrypted data appropriately.") **Related tasks** * [Create or update a variable CDI](https://servicenow-prod.fluidtopics.net/Sko5ZMaeeX_bDg4fL_WICA "Define variables and set their values in components, collections, and deployables.") * [Manage files using file nodes](https://servicenow-prod.fluidtopics.net/~RZNhiI3wHugd_UlCC_6rQ "Add and manage files using file nodes in the config data model of a CDM app or in a component library.") **Related reference** * [CDM data model](https://servicenow-prod.fluidtopics.net/ZN7eqYO5WCjS4cDDgfQaQQ "The CDM data model is a standardized data structure that supports the broader life cycle of software delivery — automation, quality validation, and CSDM. CDM imports existing config data, validates it using policies that you define, and exports valid config data to your organization's existing DevOps pipeline to implement applications, services, and infrastructure.")