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

# Change Management considerations {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Consider these points while implementing the CSDM framework.

* Business applications not referenced in the Change Management use case: Business applications are portfolio objects you can use for designing and planning an enterprise architecture. Business application portfolio objects don't contain version, environment, and localization details for deployments using one or more applications.
* Change approval process: The approval process depends on how you implement Change Management. After you populate the CIs on the Change form (if there's a relationship between the CI and the impacted services and service offerings), the Approval group approves the change.
* CI attributes used for routing changes: If you are initiating the change or the change task, use the Assignment group attribute of the CI. If you use build and run teams, you can use the Support group attribute of the CI for team assignments.

{#itsm-change-use-case-trouble__ul_d1s_v3p_rmb}

## For more information {#itsm-change-use-case-trouble__section_cfp_q1b_rmb}

[See the video: How Change Management leverages the CSDM](https://www.youtube.com/watch?v=3iCxTeU4ZTA&list=PLkGSnjw5y2U7QNr9jL6TAgwQvYBI_LEtK&index=43)