---
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


---

# Change Management properties

# Change Management properties {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Change Management properties

ServiceNow administrators can configure Change Management behavior using a variety of system properties accessible via Change \> Administration \> Change Properties.
These properties allow fine-tuning of change request approvals, risk calculations, copying attributes from originating changes, integration with Discovery, enforcement of data requirements, and event generation related to state changes.
Show full answer Show less  

## Key Configuration Areas

* **Approval and Risk Calculation:** Properties like `glide.approvalengine.changetask` control task approval workflows, while `glide.ui.riskcalculaterule` manages risk calculation methods, which can be turned off if needed.
* **Copying Change Data:** Properties such as `com.snc.changerequest.enablecopy` and related attributes lists define what fields and related list data (change tasks, affected CIs, impacted services) are copied from the originating change request to new change requests, including attachments.
* **Data Enforcement:** `com.snc.changemanagement.enforcedatarequirements` ensures consistent data validation across all modifications to change requests, covering UI, workflows, APIs, and scripts.
* **Unauthorized Changes:** The property `com.snc.changerequest.enableunauthorized` allows creation of unauthorized change requests triggered by specific system events.
* **Event Generation:** Change request state change events can be enabled and filtered by state using `com.snc.changerequest.event.stateupdated.enabled` and `com.snc.changerequest.event.stateupdated.states`.

## Discovery Integration

If Discovery is enabled in your ServiceNow instance, Change Management supports automatic or manual triggering of Discovery scans on affected configuration items (CIs) using these properties:

* `com.snc.changerequest.auto.discovery`: Controls whether Discovery runs automatically, manually, both, or not at all.
* `com.snc.changerequest.disco.auto.state` and `com.snc.changerequest.disco.manual.state`: Define the change request states where Discovery triggers automatically or can be manually triggered.

## Additional Properties

* Properties for copying related lists and attachments from originating changes.
* Debug logging for change approval policies.
* Control over CAB meeting opening behavior in the Service Operations Workspace or Core UI, governed by user roles and the `snchangecab.com.snc.changemanagement.cab.usesowmeeting` property.

## Practical Benefits for ServiceNow Customers

By configuring these properties, administrators can tailor Change Management processes to organizational policies, streamline data consistency, automate Discovery integration, and enhance visibility and control over change approvals and events. This results in more efficient change workflows, better risk management, and improved alignment with IT service management practices.  
Administrators can use change properties to configure Change Management behavior.
Navigate to ChangeAdministrationChange Properties to view and edit these properties.{#r_ChangeManagementProperties__table_qc3_qt4_p4__entry__2}

| Name | Description |
|-|-|
| glide.approval_engine.change_task | Change request tasks approval engine. * Type: choice list * Default value: process_guide {#r_ChangeManagementProperties__ul_j5r_gyt_yr} |
| glide.ui.risk_calculate_rule | Change risk calculation method. None turns off this capability. * Type: choice list * Default value: ui_action {#r_ChangeManagementProperties__ul_nbv_gyt_yr} For more information, see [Risk Calculator property](https://www.servicenow.com/docs/PcV5pwq7QHGM699nFUApoA "The Change Management- Risk Calculator plugin enables dynamic calculations of the risk and impact of a change. The administrator specifies how and when risk and impact rules are applied."). |
| com.snc.change_request.enable_copy | Enable copy change feature. * Type: true \| false * Default value: true {#r_ChangeManagementProperties__ul_kcz_y54_p4} |
| com.snc.change_request.copy.attributes | List of attributes (comma-separated) that are copied from the originating change. * Type: string * Default value: category,cmdb_ci,priority,risk,impact,type,assignment_group,assigned_to,short_description,description,change_plan,backout_plan,test_plan {#r_ChangeManagementProperties__ul_ywb_pw4_p4} |
| com.snc.change_request.copy.rl.change_task.attributes | List of attributes (comma-separated) from the Change Task \[change_task\] related list that will be copied from the originating change. * Type: string * Default value: cmdb_ci,priority,assignment_group,assigned_to,short_description,description {#r_ChangeManagementProperties__ul_mwg_mxl_j1b} |
| com.snc.change_request.copy.rl.task_ci.attributes | List of attributes (comma-separated) from the Affected CIs \[task_ci\] related list that will be copied from the originating change. * Type: string * Default value: ci_item {#r_ChangeManagementProperties__ul_hw5_nxl_j1b} |
| com.snc.change_request.attach.enable_copy | Copy attachments from the originating change. * Type: true \| false * Default value: true {#r_ChangeManagementProperties__ul_kdw_dx4_p4} |
| com.snc.change_request.copy.rl.task_cmdb_ci_service.attributes | List of attributes (comma-separated) from Impacted Services \[task_cmdb_ci_service\] related list that will be copied from the originating change. * Type: string * Default value: cmdb_ci_service {#r_ChangeManagementProperties__ul_mkl_4xl_j1b} |
| com.snc.task.refresh_impacted_services | List of all the Task types where Refresh Impacted Services action is enabled. * Type: string * Default value: incident, change_request {#r_ChangeManagementProperties__ul_p1t_hnr_ndb} |
| change.refresh_impacted.include_affected_cis | Lists the impacted CIs or Services with any service supported by a configuration item identified in the Affected CI related list. Note: This requires any business services identified to be converted to an application service. For instructions, see [Convert business services to application services](https://www.servicenow.com/docs/access?context=convert-bus-to-app-svc-intro&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). For information about application services, see [Application services](https://www.servicenow.com/docs/access?context=application-services&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). |
| com.snc.change_management.enforce_data_requirements | Enforce change request process data requirements, so that any data modification on the change request has the same data restrictions. This includes, updates made through the change request form, Workflow, REST/SOAP, JavaScript, and GlideRecord updates. For more information, see [Change Management API](https://www.servicenow.com/docs/access?context=change-management-api&version=brazil&pubname=brazil-api-reference&ft:locale=en-US) In the User Interface, when this property is true, it enables additional server sided restrictions to the UI Policy and Client Script controls that already exist. * Type: true \| false * Default value: true {#r_ChangeManagementProperties__ul_lt5_hz1_xfb} |
| com.snc.change_request.populate_service_offering | Populates the service offering related list from the impacted service list. * Type: true \| false * Default value: false {#r_ChangeManagementProperties__ul_xdg_gcd_khb} |
| com.snc.change_request.enable_unauthorized | Enables the creation of unauthorized change requests when the event ci.change.unplanned is raised. * Type: true \| false * Default value: false {#r_ChangeManagementProperties__ul_unk_cd5_g3b} |
| com.snc.change_request.event.state_updated.enabled | Generates the sn_change.state.updated event when the state of the change request is updated. * Type: true \| false * Default value: false {#r_ChangeManagementProperties__ul_alm_s3d_flb} |
| com.snc.change_request.event.state_updated.states | Enter the change request state field values, each separated by a comma to generate the sn_change.state.updated event. This happens when any of the state value changes, for example, -5, -3, 0. You can leave the property empty to generate the sn_change.state.updated event for all state changes. For more information on the state values, see [State model and transitions](https://www.servicenow.com/docs/LTYmb2Zefl1IO0LOkjc0rA "Change Management offers a state model to move and track change requests through several states."). Note: For this property to take effect, property com.snc.change_request.event.state_updated.enabled must be set to true. |
[Table 1.]

{#r_ChangeManagementProperties__table_qc3_qt4_p4}

## Change Management properties for
Discovery integration {#r_ChangeManagementProperties__section_a1k_zvb_4gb}

If your organization is subscribed to Discovery, integration with Discovery is automatically enabled. With this integration, any configuration item (CI) with an IP address that is part of a change request process can be maintained automatically. When Discovery is activated, the following three properties become available.  
{#r_ChangeManagementProperties__table_mh3_5wb_4gb__entry__2}

| Name | Description |
|-|-|
| com.snc.change_request.auto.discovery | Trigger Discovery for the Affected CIs automatically, manually or not at all. * Type: Choice list * Values: Off, Both, Automatic, Manual * Default value: Off {#r_ChangeManagementProperties__ul_kld_kv4_jdb} |
| com.snc.change_request.disco.auto.state | Defines the change request states in which Discovery is automatically triggered. * Type: String * Default value: Review {#r_ChangeManagementProperties__ul_tyg_tv4_jdb} |
| com.snc.change_request.disco.manual.state | Defines the change request states in which Discovery can be manually triggered. * Type: String * Default value: Implement, Review {#r_ChangeManagementProperties__ul_ivb_wv4_jdb} |
[ ]

{#r_ChangeManagementProperties__table_mh3_5wb_4gb}

## Change Management properties
available from sys_properties table {#r_ChangeManagementProperties__section_lrl_tvb_4gb}

The following properties are available for further configuration. To list them, enter <kbd class="ph userinput">sys_properties.list</kbd> in the navigator text box and filter for com.snc.change_.{#r_ChangeManagementProperties__table_ax1_nvt_yr__entry__2}

| Name | Description |
|-|-|
| com.snc.change_request.copy.related_lists | Related lists (comma-separated) that will be copied from the originating change. * Type: string * Default value: task_ci,task_cmdb_ci_service,change_task {#r_ChangeManagementProperties__ul_hjf_pbn_yr} |
| com.snc.change_request.rl.change_task.attach.enable_copy | Copy attachments from originating change task. * Type: true \| false * Default value: true {#r_ChangeManagementProperties__ul_jhb_nvt_yr} |
| com.snc.change_management.policy.approval.log | The debug logging property that provides the detailed logging information of the workflow activity when using Change Approval Policies. Type: choice list |
| sn_change_cab.com.snc.change_management.cab.use_sow_meeting | Controls opening of a CAB meeting from the CAB Meeting calendar in the CAB Workbench in Service Operations Workspace. Note: Users must have the sn_sow.sow_user role to open CAB meetings in SOW. * Type: true \| false * Default value: false, for upgrade customers; true for new customers. {#r_ChangeManagementProperties__ul_gyz_dkp_kfc} * true: CAB meetings open in the CAB Meeting workbench in SOW. * false: CAB meetings open in the Core UI. {#r_ChangeManagementProperties__ul_ijd_1lp_kfc} |
[ ]

{#r_ChangeManagementProperties__table_ax1_nvt_yr}

*[\>]: and then


