--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-zurich-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3bz bundleId : - delta3bz --- # Combined Developer Sandboxes release notes for upgrades from Zurich to Brazil # Combined Developer Sandboxes release notes for upgrades from Zurich to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 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 Developer Sandboxes Release Notes for Upgrades from Zurich to Brazil This consolidated guide provides ServiceNow customers with critical information on upgrading Developer Sandboxes from the Zurich release through to the Brazil release. It covers new features, changes, deprecations, and important upgrade tasks to help you prepare, execute, and optimize your sandbox environments effectively. Show full answer Show less ## Important Upgrade Information * Before upgrading to Brazil, review and complete all pre- and post-upgrade tasks to ensure smooth transition. * There were no updates to Developer Sandboxes in Zurich, Australia, or Brazil releases specifically flagged as requiring immediate action. ## New Features * **Zurich:** Introduction of the Sandbox Management home dashboard to monitor sandbox allocation, status, data utilization, and activity. Features to reuse data via sandbox templates and create data generation profiles enable efficient data setup for testing. Support for allocating and retiring sandboxes and automatic backup of update sets after upgrades. * **Australia:** Added granular roles allowing delegated developers administrative capabilities without full admin rights. AI Search now maintains separate indices per sandbox to support development activities relying on AI Search in non-production environments. * **Brazil:** Fully automated sandbox setup with self-serve license assignment through App Engine Management Center, eliminating the need for support cases. Introduction of a new licensing plugin and sandbox admin role to manage sandbox packs and licenses. Four free sandbox licenses included per non-production instance to facilitate trial use. Sandbox pooling enables faster provisioning by allocating pre-created sandboxes. Sandbox URLs are now randomly generated and immutable, while display names remain configurable. Automatic creation and removal of update set sources streamline update set transfers between production and sandbox instances. ## Key Changes * Improved upgrade experience with automatic backups and recreation of sandboxes after upgrading to address previous issues. * Schema changes to shared tables now isolate those tables on sandboxes where changes occur, ensuring configuration consistency. * Queuing mechanism introduced to enhance performance when creating multiple sandboxes consecutively. * Support added for Single Sign-On (SSO) with vanity URLs on instances. * Developer Sandboxes home page visibility is controlled by product activation status. ## Deprecations and Removals * Data generation plugin and related metadata have been deprecated and removed, with sandbox initialization now independent of data generation logic. * Sandbox alias URL and sandbox templates have been removed from the Allocate Sandbox form as URLs are now system-generated. * No features were removed between Zurich and Brazil releases. ## Activation and Licensing * **Zurich and Australia:** Activation requires contacting your ServiceNow account manager and installing Developer Sandboxes from the ServiceNow Store. * **Brazil:** Install the Developer Sandbox License Management plugin on your license management instance, deploy sandbox plugins on non-production instances, and manage licenses via App Engine Management Center. ## Highlighted Benefits for ServiceNow Customers * Work in fully isolated sandbox environments to avoid interference with teammates or the baseline instance. * Provision sandboxes on demand and align them to specific development stories or test plans to enable parallel workstreams. * Integrate Developer Sandboxes with source control (Git) to reduce merge conflicts and improve co-development workflows. * Test configurations, workflows, and integrations safely within sandboxes before promoting changes to production, minimizing rework and safeguarding system stability. This comprehensive upgrade path ensures that ServiceNow customers can leverage enhanced sandbox management, automation, and developer collaboration capabilities introduced progressively from Zurich through Brazil releases. Consolidated page of all release notes for Developer Sandboxes from Zurich to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Developer Sandboxes release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Zurich 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 Developer Sandboxes to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-developersandboxes-summary__entry__2} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Developer Sandboxes. {#dfrn3-developersandboxes-summary__entry__10} | Release | Release notes | |-|-| | Zurich | [Explore](https://www.servicenow.com/docs/access?context=exploring-sandboxes&family=zurich&ft:locale=en-US) : View the total, available, and allocated sandboxes in your instance by using the Sandbox Management home dashboard. The dashboard also displays information about each sandbox, including the status, data utilization, owner, when the sandbox was last accessed, and when the sandbox was allocated. [Using sandbox templates](https://www.servicenow.com/docs/access?context=create-sandbox-template&family=zurich&ft:locale=en-US) : Enable your delegated developers to reuse the data so that they can test their changes without manually inputting the data every time. [Create a Data Generation Profile](https://www.servicenow.com/docs/access?context=create-data-generation-profile&family=zurich&ft:locale=en-US) : Enable your customers to generate the data for testing within the context of developer sandboxes, but also independently of sandboxes. Note: Developer Sandboxes can't copy all the instance data. Data generation profiles enable a statistical sampling of data from selected tables with curated mappings to populate the sandbox with the data needed for building an application. [Allocate a sandbox](https://www.servicenow.com/docs/access?context=allocating-sandboxes&family=zurich&ft:locale=en-US) : Allocate the sandboxes that were created to your development teams. [Retire sandboxes](https://www.servicenow.com/docs/access?context=retire-sandboxes&family=zurich&ft:locale=en-US) : Retire outdated sandboxes to make room for the new sandboxes in your instance. [Automatically backed up update sets](https://www.servicenow.com/docs/access?context=dev-sbx-clone-upgrade-info&family=zurich&ft:locale=en-US) : If you install Developer Sandboxes on an instance after Zurich Patch 5, update sets are automatically backed up when the instance is upgraded. | | Australia | [New granular roles for administration](https://www.servicenow.com/docs/access?context=dsb-installed-with&family=australia&ft:locale=en-US) : Several new granular roles enable developers to complete administrative and configuration tasks without requiring the full admin role. [Support for separate indices for AI Search](https://www.servicenow.com/docs/access?context=exploring-sandboxes&family=australia&ft:locale=en-US) : AI Search (AIS) now maintains separate indices for each sandbox environment, ensuring development activities that rely on AIS are correctly supported. Note: The AIS integration with Developer Sandboxes is supported only on non-production environments. | | Brazil | [Fully automated setup with self-serve license assignment](https://www.servicenow.com/docs/access?context=dsb-license-allocation-about&family=brazil&ft:locale=en-US) : Assign purchased sandbox packs to non-production instances directly from the Developer Sandbox Management tab in App Engine Management Center (AEMC), without opening a support case. Install the new licensing plugin on your license management instance, install the sandbox plugin on your non-production instances, and use the license management UI on the controller instance to distribute packs. Each pack provides 10 sandboxes, and you can assign a maximum of 3 packs to a single non-production instance. In support, the following have been added when the new com.glide.dsb.licensing plugin is installed: * A new instance allocation table \[sys_dsb_instance_allocation\] is now installed with Developer Sandboxes. * The new sandbox admin role (`sn_dsb_commons.sandbox_license_admin`) lets users distribute sandbox packs to non-production instances without full admin access. [Four free sandbox licenses](https://www.servicenow.com/docs/access?context=dev-sbx-entitlements&family=brazil&ft:locale=en-US) : All instances now get four free sandboxes per non-production instance to try out Developer Sandboxes. You can use the four free licenses on the same instance as purchased sandboxes, for a maximum of 34 sandboxes on an instance. [Sandbox pooling for faster provisioning](https://www.servicenow.com/docs/access?context=allocating-sandboxes&family=brazil&ft:locale=en-US) : Allocate sandboxes faster using pre-pooled instances. When you allocate a sandbox, you claim one from a pre-created pool rather than waiting for a new instance to be provisioned. Sandbox URLs are randomly generated strings and no longer match the sandbox display name. The display name remains configurable, but you can't change the URL. Note: Because pooled sandboxes are precreated, they may be out of date from the current base instance state, but are refreshed every 24 hours. [Automatic update set sources](https://www.servicenow.com/docs/access?context=dsb-update-sets&family=brazil&ft:locale=en-US) : Transfer update sets between production and sandbox instances without manual configuration. When a sandbox is created, an update set source pointing to the sandbox is automatically created on the base instance, and an update set source pointing to production is automatically created on the sandbox. When a sandbox is retired, both update set sources are automatically removed. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Developer Sandboxes features. {#dfrn3-developersandboxes-summary__entry__18} | Release | Release notes | |-|-| | Zurich | [Upgrade enhancements](https://www.servicenow.com/docs/access?context=dev-sbx-clone-upgrade-info&family=zurich&ft:locale=en-US) : Automatic backups for upgrades are now working correctly. This issue is related to PRB2017438. | | Australia | [Upgrade enhancements](https://www.servicenow.com/docs/access?context=dev-sbx-clone-upgrade-info&family=australia&ft:locale=en-US) : Automatic backups for upgrades are now working correctly. This issue is related to PRB2017438. [Schema change for shared tables isolates the table](https://www.servicenow.com/docs/access?context=dsb-installed-with&family=australia&ft:locale=en-US) : To ensure configuration consistency, if you make a schema change, such as adding a column, to a shared table, the table now becomes an isolated table on the sandbox that initiated the schema change. [Upgrade enhancements](https://www.servicenow.com/docs/access?context=dev-sbx-clone-upgrade-info&family=australia&ft:locale=en-US) : After an upgrade, Developer Sandboxes now recreates the sandboxes on an instance and automatically backs up update sets to the base instance. [Queuing for successive sandbox creation](https://www.servicenow.com/docs/access?context=allocating-sandboxes&family=australia&ft:locale=en-US) : To improve performance, Developer Sandboxes has implemented queuing when multiple sandboxes are created in succession. [SSO support for vanity URLs](https://www.servicenow.com/docs/access?context=dev-sbx-general-guidelines&family=australia&ft:locale=en-US) : Instances with vanity URLs can now support Single Sign-On (SSO). [New vibe coding documentation](https://www.servicenow.com/docs/access?context=vibe-coding-landing&family=australia&ft:locale=en-US) : Documentation is now available that introduces vibe coding, which is a natural language approach to application development in ServiceNow, including how to get started, when to use it, and how it fits within the broader suite of AI-powered development tools. [Clarified sandbox initialization status](https://www.servicenow.com/docs/access?context=allocating-sandboxes&family=australia&ft:locale=en-US) : An error status message now appears on the instance home page when there's an initialization error when allocating a sandbox. [Developer Sandboxes home page hidden when product is inactive](https://www.servicenow.com/docs/access?context=dev-sbx-entitlements&family=australia&ft:locale=en-US) : The Developer Sandboxes home page is unavailable when Developer Sandboxes is inactive on an instance. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some Developer Sandboxes features or functionality were removed. {#dfrn3-developersandboxes-summary__entry__26} | Release | Release notes | |-|-| | 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 Developer Sandboxes features or functionality were deprecated. {#dfrn3-developersandboxes-summary__entry__34} | Release | Release notes | |-|-| | Zurich | * All data generation metadata and non-metadata records are automatically deleted. * The data generation plugin is no longer discoverable. * All references to data generation will be removed from sandbox templates. * Sandbox initialization will operate independently of data generation logic. | | Australia | * All data generation metadata and non-metadata records are automatically deleted. * The data generation plugin is no longer discoverable. * All references to data generation will be removed from sandbox templates. * Sandbox initialization will operate independently of data generation logic. | | Brazil | Form changes : * The Sandbox alias URL field has been removed from the Allocate Sandbox form. Because sandbox URLs are now randomly generated, you no longer specify a URL at allocation time. * Sandbox templates have been removed from the Allocate Sandbox form. | [ ] ## Activation information Review information on how to activate Developer Sandboxes. {#dfrn3-developersandboxes-summary__entry__42} | Release | Release notes | |-|-| | Zurich | Activation information : Contact your ServiceNow account manager to install Developer Sandboxes. Important: [Developer Sandboxes](https://www.servicenow.com/docs/access?context=sandboxes-landing&family=zurich&ft:locale=en-US) is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Australia | Activation information : Contact your ServiceNow account manager to install Developer Sandboxes. | | Brazil | Activation information : Install the Developer Sandbox License Management (`com.glide.dsb.licensing`) plugin on your license management instance, install the sandbox plugin on your non-production instances, and use the license management UI in App Engine Management Center on the controller instance to distribute packs. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Developer Sandboxes we have noted them here. {#dfrn3-developersandboxes-summary__entry__50} | Release | Release notes | |-|-| | 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 Developer Sandboxes we have noted them here. {#dfrn3-developersandboxes-summary__entry__58} | Release | Release notes | |-|-| | 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 Developer Sandboxes, such as specific requirements or compliance levels. {#dfrn3-developersandboxes-summary__entry__66} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Developer Sandboxes we have noted them here. {#dfrn3-developersandboxes-summary__entry__74} | Release | Release notes | |-|-| | 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 Developer Sandboxes we have noted them here. {#dfrn3-developersandboxes-summary__entry__82} | Release | Release notes | |-|-| | Zurich | * Support for Build Agent in sandboxes. * Enable your administrators and delegated developers to request, access, and manage the isolated development environments on top of the same underlying development instance. * Provide developer isolation and parallelism for customer development environments and instances. * View the total, available, and allocated sandboxes in your instance by using the Sandbox Management home dashboard. The dashboard also displays information about each sandbox, including the status, data utilization, owner, when it was last accessed, and when the sandbox was allocated. See [Developer Sandboxes](https://www.servicenow.com/docs/access?context=sandboxes-landing&family=zurich&ft:locale=en-US) for more information. | | Australia | * Support for Build Agent in sandboxes. * Upgrading an instance recreates sandboxes and backs up any update sets. * A new plugin supports clone preservation when cloning an instance with sandboxes. See [Developer Sandboxes](https://www.servicenow.com/docs/access?context=sandboxes-landing&family=australia&ft:locale=en-US) for more information. | | Brazil | * Work in fully isolated environments, so changes in one sandbox don't affect teammates, the baseline instance, or other sandboxes running in parallel. * Provision sandboxes on demand and align them to specific stories, developers, or test plans, enabling multiple workstreams to run concurrently without waiting for shared resources. * Integrate with source control (Git), reducing merge conflicts and making co-development smoother compared to shared development instances. * Safely test configurations, workflows, and integrations within your own sandbox before promoting changes, reducing rework and protecting system stability. See [Developer Sandboxes](https://www.servicenow.com/docs/access?context=sandboxes-landing&family=brazil&ft:locale=en-US) for more information. | [ ]