---
sourceDocument: brazil Combined Product Files
sourceDocumentLink: https://www.servicenow.com/docs/r/delta-yokohama-brazil

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - brazil Combined Product Files

ft:clusterId :

    - delta3by

bundleId :

    - delta3by


---

# Combined Change Management release notes for upgrades from Yokohama to Brazil

# Combined Change Management release notes for upgrades from Yokohama to Brazil {#ariaid-title1}

Release version: Brazil  
Updated October 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 13 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 Combined Change Management Release Notes for Upgrades from Yokohama to Brazil

This consolidated release notes document assists ServiceNow customers in upgrading Change Management from the Yokohama release to Brazil.
It provides essential information on new features, changes, deprecations, and upgrade considerations across the Zurich, Australia, and Brazil releases.
The document aims to prepare customers for a smooth upgrade process while highlighting security, usability, and compliance improvements.
Show full answer Show less  

## Important Upgrade Information

* **Enhanced Security Features Plugin Activation:** Automatically activated starting with Zurich, Australia, and Brazil releases. This plugin enforces "deny unless authenticated" access control lists (ACLs) on core ITSM tables like `changerequest` and `changetask`. Customers upgrading existing instances should test ACL impacts in sub-production and may contact ServiceNow Support to revert ACL changes if necessary.
* **Conflict Detection Mechanism Update:** Zurich introduced a switch from Progress Workers to Flow-based conflict detection using the Change Management Worker table, configurable via the `change.conflict.useprogressworker` system property. UI formatters also adapt based on this property.

## Key Features Introduced Between Yokohama and Brazil

* **snservicedeskagent Role:** Designed for tier 1 service desk agents to improve efficiency in incident, problem, change, and request management. Integrates with ITSM Gen AI roles when applicable and works with Service Operations Workspace 6.1+.
* **Change Model Enhancements:** Addition of a new "Model" option in the change model Type field to identify controlled changes, with state field policies enforcing mandatory and read-only fields per state.
* **Risk Assessment Improvements:** The Risk field no longer has a default value on change requests, requiring explicit risk evaluation to ensure accuracy.
* **Mandatory Field Transition Conditions:** Change managers can enforce completion of required fields before progressing change states per change model rules.
* **Granular Administration Role:** The `snchangeadmin` role consolidates permissions for managing Change Management features and system properties, replacing broader admin roles.
* **Change Templates \& Enhanced Data Model:** Standardized templates for change models allow control over mandatory/read-only fields and support versioning and lifecycle management. Enhanced data models enable better categorization and role-based template access without impacting existing standard changes.
* **Compliance Dynamic Schema:** Stores risk and compliance attributes as dynamic name-value pairs within a single field, facilitating compliance data capture without extending the Change Request table schema. Supports industry-specific requirements such as audit trails and rollback times.
* **Change Lockdown:** Allows pausing of all or subsets of in-flight changes during critical events. Changes overlapping lockdown periods are automatically flagged and placed on hold until rescheduled.
* **Scaled Change:** Manages complex environments by generating and coordinating child change records per affected configuration item, leveraging scheduling intelligence, conflict detection, and approval workflows.
* **ITIL Change Process Assignment:** Assign ITIL processes directly to change models to automate correct process usage during change request creation via API.
* **Conflict Detection Enhancements:** Ability to exclude specific change requests from conflict checks and limit maximum conflict records generated per type via system properties.

## Notable Changes

* **Coral Theme:** Zurich introduced the Coral theme as the default for portals and UI with a modern look and a dark mode option to improve user experience.
* **Workflow to Flow Transition:** Change Management workflows have been fully replaced by Flow Designer flows for new customers, offering improved customization and extensibility.

## Accessibility and Usability Enhancements

* **Reflow Support:** The Create a Change Request page supports up to 400% zoom with automatic layout adjustments for better accessibility, addressing low vision and device constraints. This feature can be disabled via system property.
* **Dark Theme Option:** Coral theme's dark mode helps reduce eye strain and improve readability for web and mobile users.

## Practical Implications for ServiceNow Customers

* Expect enhanced security by default through ACLs protecting Change Management tables, requiring thorough testing before production deployment.
* Leverage new roles like `snservicedeskagent` and `snchangeadmin` to better align user permissions with operational needs.
* Utilize change templates and dynamic compliance schemas to improve change standardization, compliance tracking, and audit readiness without database schema changes.
* Apply change lockdown and scaled change capabilities to manage risk during critical periods and complex change environments effectively.
* Benefit from improved UI themes and accessibility features to enhance change management user adoption and satisfaction.

## Next Steps for Customers

* Review and complete pre- and post-upgrade tasks, paying special attention to security plugin activation and ACL impacts.
* Test new conflict detection configurations and UI changes in a sub-production  
Consolidated page of all release notes for Change Management from Yokohama to Brazil.

## How to use this page

To help you prepare for your upgrade, we have combined the cross-family Change Management release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Brazil.  
Tip:  
If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

## Important information for upgrading Change Management to Brazil

Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed.  
{#dfrn3-changemanagement-summary__entry__2}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | Upgrade information :   As part of the update to use Flow instead of Progress Workers for conflict detection, the Conflict Checker Progress UI Formatter record references a new UI macro, change_conflict_worker_progress_gate. This macro checks the change.conflict.useprogressworker system property to determine the conflict detection mechanism and then displays the corresponding UI macro to work with either Progress Workers or the Change Management Worker table. For more information, see [Conflict detection](https://www.servicenow.com/docs/access?context=c_ConflictDetection&family=zurich&ft:locale=en-US). The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Zurich release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. |
| Australia | Upgrade information :   The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Australia release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. |
| Brazil | Upgrade information :   The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Brazil release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. |
[ ]

## New features

Between your current release family and Brazil, new features were introduced for Change Management.  
{#dfrn3-changemanagement-summary__entry__12}

| Release | Release notes |
|-|-|
| Yokohama | [User role for service desk agents](https://www.servicenow.com/docs/access?context=installed-with-cm-itsm-roles&family=yokohama&ft:locale=en-US) :   With the sn_service_desk_agent user role, increase operational efficiency by streamlining the process of asking about, gathering, and verifying information, as well as delivering quick resolutions. This role is designed for tier 1 service desk agents and is accessible when the ITSM Roles plugin (com.snc.itsm.roles) installed. The sn_service_desk_agent role includes the following roles: * sn_incident_write * sn_problem_write * sn_change_write * sn_request_write * tracked_file_reader Additionally, with the installation of the ITSM Gen AI (com.sn.itsm.gen.ai) plugin, the knowledge_user and now_assist_panel_user roles are integrated within the sn_service_desk_agent role. The sn_service_desk_agent user role can be used starting with Service Operations Workspace version 6.1. [Change model Type field](https://www.servicenow.com/docs/access?context=t_CreateAChange&family=yokohama&ft:locale=en-US) :   A new Model option has been added to the change model Type field to help users identify a change that is controlled by a change model. Model is the default if a Type has not been set for the change request of a certain change model. [No default Risk value for change requests](https://www.servicenow.com/docs/access?context=t_CreateAChange&family=yokohama&ft:locale=en-US) :   There is no longer a default value for the Risk field on the Change Request table. The Risk value is set to -- None -- until the risk is evaluated for the change request. This change ensures that no risk value is pre-assigned, allowing for a more accurate assessment before advancing the change [Mandatory field transition condition](https://www.servicenow.com/docs/access?context=create-a-change-model&family=yokohama&ft:locale=en-US) :   Ensure mandatory fields are completed before advancing through states for a change request, as defined by the Change Model. This feature enables change managers to mandate the completion of required fields before states can progress according to the Change Model. [Deny-unless ACLs on core tables](https://www.servicenow.com/docs/access?context=features-itsm-enhanced-security-change&family=yokohama&ft:locale=en-US) :   Prevent unauthorized access to change_request and change_task tables using deny-unless ACLs. The deny-unless ACLs restrict access on these tables for a non-authenticated user to perform actions such as read, write, delete, or create. This feature is available for new or zBoot customers with the installation of the ITSM Enhanced Security Features (com.snc.itsm.enhanced_security) plugin. Existing or upgrade customers must test and evaluate in their sub production instance before installing the plugin and implementing the security change in their production instance. |
| Zurich | [Control opening of CAB meetings](https://www.servicenow.com/docs/access?context=attend-cab-meeting-using-cab-workbench&family=zurich&ft:locale=en-US) :   Control the opening of a CAB meeting from the CAB Meeting calendar in the CAB Meeting workbench in Service Operations Workspace or in the Core UI through the sn_change_cab.com.snc.change_management.cab.use_sow_meeting system property. For more information, see [Change Management properties](https://www.servicenow.com/docs/access?context=r_ChangeManagementProperties&family=zurich&ft:locale=en-US). [Track conflict detection](https://www.servicenow.com/docs/access?context=c_ConflictDetection&family=zurich&ft:locale=en-US) :   Track the progress of conflict detection using the Change - Conflict Detection flow (that runs as a system user) and the Change Management Worker table instead of Progress Workers. You can choose between the Flow and Progress Worker options by updating the change.conflict.useprogressworker system property.A new UI formatter change_conflict_worker_progress_gate.xml has been introduced to the change request form to replace the existing change_request_conflict_progress.xml . This update supports the change.conflict.useprogressworker system property when you upgrade to Zurich. The new formatter displays the same Conflict tab but selects the macro version to render the form according to the value of the new system property. [Define the maximum records for conflict detection](https://www.servicenow.com/docs/access?context=configure-conflict-properties&family=zurich&ft:locale=en-US) :   Limit the maximum number of conflict records that can be generated for each conflict type when conflict detection runs through the change.conflict.max_count system property; create this system property if it is not already present. |
| Australia | [Granular admin role](https://www.servicenow.com/docs/access?context=installed-with-cm-itsm-roles&family=australia&ft:locale=en-US) :   Assign the single feature-specific granular sn_change_admin role to users to grant permission to configure Change Management features and system properties. This role replaces the previous general admin and ITIL roles. The sn_change_admin role includes the sn_change_writer, change_manager, and sn_change_cab.cab_manager roles. [Exclude change request records from conflict check](https://www.servicenow.com/docs/access?context=configure-conflict-properties&family=australia&ft:locale=en-US) :   Exclude change requests from the conflict check process by setting the Exclude from conflict detection field to true. This setting also means that the change record is not displayed as a conflicting change when conflict checker is run on other change records. [Create change templates](https://www.servicenow.com/docs/access?context=create-change-template&family=australia&ft:locale=en-US) :   Control mandatory and read-only fields for change models by configuring change templates and defining template field policies. Change templates provide baseline standardization for common changes, making changes easier to create as well as driving a higher standard of change and compliance. Similar to the concepts used for existing standard change templates, templates used for change models can be proposed, reviewed, versioned, or retired. [Enhanced data model for change templates](https://www.servicenow.com/docs/access?context=change-data-model&family=australia&ft:locale=en-US) :   Use the enhanced data model that supports better categorization and role-based access for change templates for all change models automatically. This feature is optional for newly created standard changes. This data model does not impact the existing standard change catalog and migration of these standard changes is not required. |
| Brazil | [Compliance dynamic schema](https://www.servicenow.com/docs/access?context=compliance-dynamic-schema&family=brazil&ft:locale=en-US) :   Store risk and compliance details on change requests without adding columns to the Change Request table. Compliance dynamic schema saves these details as name and value pairs in a single field using the platform Dynamic Schema feature. Regulated industries can capture information such as whether a change handles personal data, whether an audit trail is required, and how long a rollback takes. The base system includes example dynamic categories such as Risk and Compliance, Financial Risk and Compliance, and SaaS/Cloud Security Compliance, and example attributes covering areas such as audit trail, downtime, estimated impacted users, lead time, rollback time, and compliance. You can deactivate the examples and define categories and attributes that match your organization's compliance requirements. You can also read and update attribute values from scripts, including risk condition scripts and business rules, using the dynamic schema scripting API. [Change lockdown](https://www.servicenow.com/docs/access?context=change-lockdown&family=brazil&ft:locale=en-US) :   Change lockdown allows change managers to pause all or a subset of in-flight change requests. Use it during major unplanned IT, critical, or financial events. [Change lockdown conflict detection](https://www.servicenow.com/docs/access?context=lockdown-conflict-detection&family=brazil&ft:locale=en-US) :   Automatically flag change requests that overlap an active lockdown period. Conflict detection runs alongside maintenance window and blackout window checks. Any change request inside a lockdown is marked as an Inside Change Lockdown conflict and placed on hold. Reschedule it outside the lockdown period to clear the conflict and continue processing. [Scaled change](https://www.servicenow.com/docs/access?context=scaled-change-overview&family=brazil&ft:locale=en-US) :   Scaled Change extends change management to complex environments with many configuration items. A single Scaled Change generates and coordinates child change records for every affected configuration item. It uses scheduling intelligence, conflict detection, and approval workflows to keep large-scale changes on track from planning through closure. [ITIL change process assignment for change models](https://www.servicenow.com/docs/access?context=itil_change_process_models&family=brazil&ft:locale=en-US) :   Assign an ITIL change process to a change model so the ChangeRequest API uses that model when it creates a matching change request. [State field policies for change models](https://www.servicenow.com/docs/access?context=state-field-policies-change-models&family=brazil&ft:locale=en-US) :   Use state field policies to make change request fields mandatory or read-only at each state in a change model. Policies are enforced on the form when a change request is created or updated. |
[ ]

## Changes

Between your current release family and Brazil, some changes were made to existing Change Management features.  
{#dfrn3-changemanagement-summary__entry__22}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | Coral theme :   Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Propose a standard change template in Service Operations Workspace](https://www.servicenow.com/docs/access?context=propose-standard-change-sow&family=zurich&ft:locale=en-US) :   As a user with the itil role, you can create a standard change template proposal in Service Operations Workspace. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Removed

Between your current release family and Brazil, some Change Management features or functionality were removed.  
{#dfrn3-changemanagement-summary__entry__32}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Deprecations

Between your current release family and Brazil, some Change Management features or functionality were deprecated.  
{#dfrn3-changemanagement-summary__entry__42}

| Release | Release notes |
|-|-|
| Yokohama | Change Management workflows have been removed and replaced by flows for new customers. Existing customers that use these workflows are unaffected. The flows are available to both new and existing customers. You can use ServiceNow® Workflow Studio to customize or extend these flows. For more information, see [Flow Designer](https://www.servicenow.com/docs/access?context=flow-designer&family=yokohama&ft:locale=en-US). |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Activation information

Review information on how to activate Change Management.  
{#dfrn3-changemanagement-summary__entry__52}

| Release | Release notes |
|-|-|
| Yokohama | Activation information :   Change Management is a ServiceNow AI Platform feature that is active by default. |
| Zurich | Activation information :   Change Management is a ServiceNow AI Platform feature that is active by default. |
| Australia | Activation information :   Change Management is a ServiceNow AI Platform feature that is active by default. The Change Management plugins listed are activated by default. |
| Brazil | Activation information :   Change Management is a ServiceNow AI Platform feature that is active by default. The Change Management plugins listed are activated by default. |
[ ]

## Additional requirements

If any additional requirements were introduced or changed for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__62}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Browser requirements

If any specific browser requirements were introduced or changed for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__72}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Accessibility information

Review details on accessibility information for Change Management, such as specific requirements or compliance levels.  
{#dfrn3-changemanagement-summary__entry__82}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | Accessibility information : Dark theme :   The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. |
| Australia | Accessibility information : Reflow for Create a change request page :   The Create a change request page now supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. Additionally, content can be enlarged without scrolling in two dimensions at a width equivalent to 320 CSS pixels or a height equivalent to 256 CSS pixels. Page layouts are transformed into a vertical, stacked view automatically when users increase browser zoom to 400%. This enhancement helps users with low vision or who have trouble seeing web content in a browser due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off with a system property for instances, experiences, and pages. |
| Brazil | Accessibility information :   Reflow support for the Create a change request page: Content can be zoomed up to 400% through your browser settings, with page layouts automatically transforming into a vertical, stacked view without loss of content or functionality. This enhancement helps users with low vision or who have trouble seeing web content due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off with a system property for instances, experiences, and pages. |
[ ]

## Localization information

If there are specific localization considerations for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__92}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Highlight information

If there are specific highlight considerations for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__102}

| Release | Release notes |
|-|-|
| Yokohama | * Increase operational efficiency of tier 1 service desk agents with the dedicated sn_service_desk_agent role. * Require specified field details to be updated before transitioning the state of a change request by converting existing optional fields to mandatory fields. * Restrict unauthorized access to Change Management tables using deny ACLs. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=yokohama&ft:locale=en-US) for more information. |
| Zurich | * Review and authorize change requests and review recently implemented changes in the Change Advisory Board Workbench in the Service Operations Workspace (SOW). * Track conflict detection using the Change - Conflict Detection flow and the Change Management Worker table instead of Progress Workers. * Limit the number of conflict records for each conflict type through the change.conflict.max_count system property. * Coral is the new default theme for Next Experience and Core UI, offering a more modern experience. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=zurich&ft:locale=en-US) for more information. |
| Australia | * Configure the properties in Change Management application using the sn_change_admin role. * Manage conflict detection for change request using the new Exclude from conflict detection option. * Configure change templates with a specific change model. * Use change templates to manage the change request creation process. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=australia&ft:locale=en-US) for more information. |
| Brazil | * Control the full change lifecycle from request to closure using a structured workflow that reduces IT service disruption. * Define change models using custom state models, state transitions, and transition conditions. Out-of-the box change models include ITIL change models for Standard, Normal, or Emergency changes with dedicated approval paths. * Use machine learning to assess change risk and suggest standard change templates. * Run agentic AI workflows through a conversational interface. Use it to plan changes, assess conflicts, assess change quality, schedule changes, suggest configuration items, create outages, and generate standard change template proposals. * Track team performance with the Change Success Score, which uses historical data to predict successful change completion. This feature requires an ITSM Professional subscription. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=brazil&ft:locale=en-US) for more information. |
[ ]