---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# DevOps change request attributes

# DevOps change request attributes {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 DevOps Change Request Attributes

ServiceNow enables customers to add or update DevOps change request attributes using multiple methods such as the changeInfo REST API, Default Change Handler subflow, pipeline steps, Update functions, and automated approval flows.
These capabilities provide flexibility in managing change request data throughout the DevOps orchestration process.
Show full answer Show less  

## Specifying Change Request Attributes

* **REST API:** Use the DevOps PUT /devops/orchestration/changeInfo/{changeInfo} API to update fields within a specific change request. Note that this API cannot be used when the pipeline is paused or waiting.
* **Default Change Handler Subflow:** Automatically populate change request fields with default values during orchestration.
* **Pipeline Passing:** Pass change attributes directly through orchestration pipeline steps or the Update function for Azure DevOps and Jenkins pipelines.
* **Automated Flows:** Use DevOps approval flows to update change request attributes as part of approval processes.
* **Custom Actions:** Implement custom pipeline actions using Docker images or GitHub Marketplace integrations.

## Precedence and Conflict Management

When attributes are set through multiple methods simultaneously, ServiceNow follows defined precedence rules to determine which values apply:

* **Type-Based Changes:** For standard changes, attributes passed through the pipeline take precedence, followed by step record fields, then templates. For non-standard changes, pipeline attributes, Default Change Handler, and approval flows have precedence.
* **Model-Based Changes:** Model presets generally have the highest precedence, followed by pipeline attributes, Default Change Handler, and approval flows.

**Important:** Setting attribute values in both the Default Change Handler subflow and approval flows can cause conflicts because they may run simultaneously. Customers should configure attribute values in only one of these sources to avoid issues.

## Configuration Considerations

Customers using business rules in change operations should enable the `sndevops.changerequest.applyattributesoncreation` property to true. This ensures attributes passed through the pipeline are applied at change request creation rather than afterward.

## Practical Examples

* **Scenario 1:** Attributes in Default Change Handler subflow override Update function values at creation; Update function values apply after approval.
* **Scenario 2:** Pipeline change step attributes override Default Change Handler values at creation; Default Change Handler values apply afterward.
* **Scenario 3:** Attributes passed via templates in change attributes override those in pipeline step record templates during creation.
* **Scenario 4:** For model-based changes, model presets take precedence over attributes passed in change attributes.

## Key Benefits for ServiceNow Customers

* Flexible methods to define and update change request attributes that integrate seamlessly with DevOps pipelines.
* Clear precedence rules help manage attribute conflicts and ensure consistent change request data.
* Support for automated flows and custom actions enables advanced orchestration and approval scenarios.
* Configuration properties allow fine-tuning of attribute application timing for business rule compatibility.  
Add or update DevOps change request attributes using the changeInfo REST API, the Default Change Handler subflow, by passing attributes through the pipeline, Update function, or automated flows.

## Specifying attributes {#apis-for-change-actions-in-devops__section_pwr_qgq_ydc}

Use one of the following methods to specify change request attributes:

* [DevOps - PUT /devops/orchestration/changeInfo/{changeInfo}](https://www.servicenow.com/docs/access?context=devops-api&version=australia&pubname=australia-api-reference&section=devops-PUT-orch-changeInfo&ft:locale=en-US) to update fields within a specified change request.  
  Note:  
  * The changeInfo API won't function when the pipeline is in the paused state.
  * An API call can't be executed while the pipeline is waiting.
  * The API approach must be considered after thorough testing.
  {#apis-for-change-actions-in-devops__ul_ivz_lh5_ldc}
* Default Change Handler subflow to populate change request fields with default values. For more information, see [Default Change Handler subflow](https://www.servicenow.com/docs/qL5ZkK2bE2766F_f0ltR7w "Customize or recreate the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, and DevOps Change Request Advanced Automation Approval flows based on your requirements using a flow or a script.").
* Passing the change attributes through the orchestration pipeline. For more information, see [Configuring DevOps change request details within the pipeline](https://www.servicenow.com/docs/JrPZPSHCjQRzCnCP7jFB5Q "Configure how the closure information, change state, and change request fields are updated from within a pipeline in the change step of the pipeline.").
* Passing the change attributes through the Update function in the orchestration pipeline function. For more information, see the following:
  * [Get and update change request details in Azure DevOps pipeline](https://www.servicenow.com/docs/HFCD40KpQJRpiIaQ7~jgcw "Get and update the change request details associated with an Azure DevOps pipeline.")
  * [Update change request details in Jenkins pipeline](https://www.servicenow.com/docs/S7skx64jHmvPVjM03v82xg "Update the change request details associated with a Jenkins pipeline by running the snDevOpsUpdateChangeInfo script in the pipeline.")
  * [ServiceNow DevOps custom actions from GitHub marketplace](https://www.servicenow.com/docs/8IIHLttsKDPIeqy0xNUBZg#servicenow-devops-custom-actions-from-github-marketplace "Use the custom actions from the GitHub marketplace to collect scan data, manage workflows, and update change request details.")
  * [Implement custom actions for pipelines using Docker image](https://www.servicenow.com/docs/lyDd5Y1L9yyAuDzJFwe0tg "Use the ServiceNow custom actions to collect data related to change request creation, Sonar scan, artifact registration, and package registration in your pipeline with the help of the generic Docker Container Image.")
  {#apis-for-change-actions-in-devops__ul_odg_b3m_ldc}
* Automated flows: DevOps approval flows to make changes in a change request. For more information, see [Flows](https://www.servicenow.com/docs/1IOGCXHTnX02RprvPaB2wg "Enable the change acceleration feature of DevOps Change Velocity for automatic change request creation in your pipeline, and use change approval flows and policies to automate approval under certain conditions.").
{#apis-for-change-actions-in-devops__ul_w5v_lrr_3dc}

## Precedence of consideration {#apis-for-change-actions-in-devops__section_jr1_tgq_ydc}

When the change attributes are specified through multiple methods, the precedence in which the attribute values are considered will vary. In ServiceNow, attributes can be specified in the pipeline
step of DevOps Change Velocity, in the Default Change Handler subflow, or in an approval flow. In the orchestration tool pipeline, attributes can be passed in the pipeline step, or using the REST APIs. If a change model is
used, they can also be specified in model presets.

See the following tables and examples to understand the precedence in which the values will be considered.  
{#apis-for-change-actions-in-devops__table_gzf_mzr_5dc__entry__2}

| Change request | Precedence |
|-|-|
| Standard | 1. Change attributes passed through pipeline 2. Step record fields in ServiceNow 3. Template passed in change attributes through pipeline 4. Template in Step fields in ServiceNow {#apis-for-change-actions-in-devops__ol_mdw_xzr_5dc} |
| Non-standard | 1. Change attributes passed through pipeline 2. Default Change Handler subflow \& approval flows Important: Setting attribute values in both the Default Change Handler subflow and approval flows can cause conflicts because they might run simultaneously. Set the attribute values in only one source to avoid issues. 3. Step record fields in ServiceNow 4. Template passed in change attributes through pipeline 5. Template in Step fields in ServiceNow {#apis-for-change-actions-in-devops__ol_opz_zzr_5dc} |
[Table 1. Precedence of change attributes for type-based changes]

{#apis-for-change-actions-in-devops__table_gzf_mzr_5dc}  
{#apis-for-change-actions-in-devops__table_tyh_31s_5dc__entry__2}

| Change request | Precedence |
|-|-|
| Standard | 1. Model Presets 2. Change attributes passed through pipeline 3. Step record fields in ServiceNow 4. Template passed in change attributes through pipeline 5. Template in Step fields in ServiceNow {#apis-for-change-actions-in-devops__ol_hbn_r1s_5dc} |
| Non-standard | 1. Model Presets 2. Change attributes passed through pipeline 3. Default Change Handler subflow \& approval flows Important: Setting attribute values in both the Default Change Handler subflow and approval flows can cause conflicts because they might run simultaneously. Set the attribute values in only one source to avoid issues. 4. Step record fields in ServiceNow 5. Template passed in change attributes through pipeline 6. Template in Step fields in ServiceNow {#apis-for-change-actions-in-devops__ol_vyh_31s_5dc} |
[Table 2. Precedence of change attributes for model-based changes]

{#apis-for-change-actions-in-devops__table_tyh_31s_5dc}  
Note:  
If you have used business rules in your change operations, then you must set the sn_devops.change_request.apply_attributes_on_creation property to true, so that the change attributes passed in the pipeline are set when the change request is created instead of the attributes being passed after the change request is created. For more information, see [DevOps Change Velocity properties](https://www.servicenow.com/docs/Cy67V7Lf9sOXU2beB3VARQ "Use these properties to configure settings in the DevOps Change Velocity application.").  

## Scenario 1 {#apis-for-change-actions-in-devops__example_ol4_bdq_wdc}

Consider a scenario where the attributes are specified in the Default change handler subflow in
ServiceNow and in the Update function in the orchestration pipeline. Assume that the assignment_group attribute is specified as "change mgmt" in the Default change handler subflow, and as "CAB" in the Update function in the
pipeline. In this scenario, when the change is created, the value from the Default change handler subflow will be considered, and "change mgmt" will be the value considered for assignment_group. Once the change is approved,
and the pipeline is resumed, the value specified in the Update function will be considered, i.e. "CAB".  

## Scenario 2 {#apis-for-change-actions-in-devops__example_uzc_2dq_wdc}

Consider a scenario where the attributes are specified in the Default change handler subflow in
ServiceNow and in the change step in the orchestration pipeline. Assume that the assignment_group attribute is specified as "change mgmt" in the Default change handler subflow, and as "chg mgmt1" in the change step of the
pipeline. In this scenario, when the change is created, the value from change step (chg mgmt1) will be considered, and then once the Default change handler subflow is triggered, the value considered will be "change
mgmt".  

## Scenario 3 {#apis-for-change-actions-in-devops__example_olc_xy4_ydc}

Consider a scenario where the attributes are specified through the template passed in change
attributes and in the template of the step record. Assume that the assignment_group attribute is specified as "change mgmt" in the template passed in change attributes, and as "chg mgmt1" in the template of the pipeline step
record. In this scenario, when the change is created, the value from the template passed in change attribute (chg mgmt) will be considered.  

## Scenario 4 {#apis-for-change-actions-in-devops__example_kxr_2z4_ydc}

Consider a scenario where the attributes are specified in the change attributes and the model preset for a model-based change. Assume that the assignment_group attribute is specified as "change mgmt" in change attributes and
as "chg mgmt1" in the model preset. In this scenario, when the change is created, the value from model preset (chg mgmt1) will be considered.