Change Management properties

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
    • Summarize
    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 the behavior of Change Management by using various system properties accessible viaChange > Administration > Change Properties. These properties allow control over approval processes, risk calculations, feature enablement, integration with Discovery, and more, enabling tailored management of changes within the platform.

    Show full answer Show less

    Key Features

    • Approval Engine Configuration: The glide.approvalengine.changetask property lets admins select the approval engine used for change request tasks.
    • Risk Calculation Methods: The glide.ui.riskcalculaterule property sets how risk is calculated—either via business rule on insert/update or UI action on demand. It can also be disabled.
    • Copy Change Feature: Enable or disable copying of change requests and related attributes using properties such as com.snc.changerequest.enablecopy and attribute lists for changes, tasks, affected CIs, and impacted services. Attachment copying is separately controlled.
    • Refresh Impacted Services: Define which task types support the "Refresh Impacted Services" action, typically including incidents and change requests.
    • Data Enforcement: The com.snc.changemanagement.enforcedatarequirements property enforces consistent data restrictions across UI, workflows, APIs, and scripts, improving data integrity.
    • Unauthorized Changes: Enable creation of unauthorized change requests when specific events occur, controlled by com.snc.changerequest.enableunauthorized.
    • Event Generation: Properties control the generation of change state update events, allowing event-driven integrations and notifications.
    • Discovery Integration: When Discovery is enabled, properties control automatic or manual triggering of Discovery scans on affected CIs during certain change request states, enhancing CI data accuracy.
    • Additional Configurations: Properties include controls for copying related lists, copying attachments on change tasks, detailed logging for approval policies, and CAB meeting handling in Service Operations Workspace.

    Key Outcomes

    • Administrators gain granular control over Change Management processes, improving alignment with organizational policies and workflows.
    • Risk assessment and approval workflows can be tailored for better governance and efficiency.
    • Copying features streamline the creation of new changes from existing ones, saving time and reducing manual data entry errors.
    • Integration with Discovery ensures that affected configuration items are accurately maintained within change requests.
    • Event generation and enforcement of data requirements support automation and consistent data quality across change processes.
    • Flexibility in CAB meeting handling enables better collaboration within the preferred user interface environment.

    Administrators can use change properties to configure Change Management behavior.

    Navigate to Change > Administration > Change Properties to view and edit these properties.
    Table 1. Change Management properties
    Name Description
    glide.approval_engine.change_task Change request tasks approval engine.
    • Type: choice list
    • Default value: process_guide
    glide.ui.risk_calculate_rule Change risk calculation method. Business rule calculates on insert/update, UI action calculates only on demand. None disables this capability.
    • Type: choice list
    • Default value: ui_action

    For more information, see Risk Calculator property.
    com.snc.change_request.enable_copy Enable copy change feature.
    • Type: true | false
    • Default value: true
    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
    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
    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
    com.snc.change_request.attach.enable_copy Copy attachments from the originating change.
    • Type: true | false
    • Default value: true
    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
    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
    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. For information about application services, see Application services.
    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

    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
    com.snc.task.populate_service_offering Populates the service offering related list from the impacted service list.
    • Type: true | false
    • Default value: false
    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
    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
    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 Legacy: State model and transitions.
    Note:
    For this property to take effect, property com.snc.change_request.event.state_updated.enabled must be set to true.

    Change Management properties for Discovery integration

    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 new properties become available.

    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
    com.snc.change_request.disco.auto.state Defines which Change Request states Discovery will be automatically triggered.
    • Type: String
    • Default value: Review
    com.snc.change_request.disco.manual.state Defines which Change Request states allow Discovery to be manually triggered.
    • Type: String
    • Default value: Implement, Review

    Change Management properties available from sys_properties table

    The following properties are available for further configuration. To list them, enter sys_properties.list in the navigator text box and filter for com.snc.change_.
    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
    com.snc.change_request.rl.change_task.attach.enable_copy Copy attachments from originating change task.
    • Type: true | false
    • Default value: true
    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.
    • true: CAB meetings open in the CAB Meeting workbench in SOW.
    • false: CAB meetings open in the Core UI.