--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined Developer Sandboxes release notes for upgrades from Australia to Brazil # Combined Developer Sandboxes release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 Australia to Brazil This consolidated release notes document provides ServiceNow customers with a comprehensive guide to Developer Sandboxes upgrades from the Australia release family to the Brazil release family. It highlights new features, changes, deprecations, and important upgrade tasks to help customers effectively manage their sandbox environments during and after the upgrade process. Show full answer Show less ## Key Features * **Granular Roles for Administration (Australia):** Introduces fine-grained roles allowing developers to perform administrative and configuration tasks without requiring full admin privileges, enhancing security and delegation. * **AI Search Support (Australia):** Developer Sandboxes now maintain separate AI Search indices per sandbox environment, ensuring accurate AI-driven development activities on non-production instances. * **Fully Automated Sandbox Setup (Brazil):** Enables self-service assignment of purchased sandbox packs via the Developer Sandbox Management tab in App Engine Management Center, eliminating the need for support cases. * **Sandbox Licensing Enhancements (Brazil):** * New licensing plugin (com.glide.dsb.licensing) manages sandbox packs and supports up to three packs (30 sandboxes) per non-production instance. * Four free sandbox licenses per non-production instance allow trial use alongside purchased sandboxes, supporting up to 34 sandboxes per instance. * **Sandbox Pooling for Faster Provisioning (Brazil):** Sandboxes are allocated from pre-pooled instances, reducing provisioning time. Sandbox URLs are now randomly generated and immutable, while display names remain configurable. * **Automatic Update Set Source Management (Brazil):** Update set sources between production and sandbox instances are created and removed automatically during sandbox lifecycle events, simplifying update set transfers. ## Changes * **Upgrade Enhancements (Australia):** * Automatic backups during upgrades now function correctly, ensuring update sets are preserved. * Schema changes to shared tables isolate those tables in the sandbox where changes are made, maintaining configuration consistency. * Developer Sandboxes recreate sandboxes post-upgrade and automatically back up update sets to the base instance. * **Performance Improvements (Australia):** Queuing has been implemented for successive sandbox creation to improve system performance. * **SSO Support (Australia):** Vanity URL instances can now support Single Sign-On, enhancing user authentication experiences. * **Developer Experience Updates (Australia):** * New documentation on vibe coding, a natural language development approach, supports developers in leveraging AI-powered tools. * Sandbox initialization errors are clearly indicated on the instance home page. * The Developer Sandboxes home page is hidden when the product is inactive. * **Form Changes (Brazil):** The Sandbox alias URL field and sandbox templates have been removed from the Allocate Sandbox form since sandbox URLs are randomly generated. ## Deprecations * **Data Generation Plugin (Australia):** Data generation metadata and records are automatically deleted, and the plugin is no longer available. Sandbox initialization now operates independently from data generation logic. ## Activation and Licensing * **Australia Release:** Customers should contact their ServiceNow account manager to install Developer Sandboxes. * **Brazil Release:** Installation of the licensing plugin on the license management instance and sandbox plugin on non-production instances is required, with sandbox packs distributed via the license management UI in App Engine Management Center. ## Additional Highlights * Developer Sandboxes now support isolated environments where changes in one sandbox do not impact teammates or the baseline instance. * On-demand sandbox provisioning aligns with specific development stories, enabling parallel workstreams without resource contention. * Integration with source control (Git) reduces merge conflicts and facilitates smoother co-development compared to shared development instances. * Safe testing of configurations, workflows, and integrations within personal sandboxes reduces rework and protects system stability. ## Practical Impact for ServiceNow Customers Upgrading Developer Sandboxes from Australia to Brazil enables more efficient sandbox management, enhanced security through granular roles, faster provisioning, and streamlined licensing. Customers benefit from improved developer productivity, better control over sandbox environments, and simplified update set handling. The automated features reduce administrative overhead while supporting concurrent development workstreams safely and effectively. Consolidated page of all release notes for Developer Sandboxes from Australia 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 Australia 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 | |-|-| | 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__8} | Release | Release notes | |-|-| | 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__14} | Release | Release notes | |-|-| | 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__20} | Release | Release notes | |-|-| | 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__26} | Release | Release notes | |-|-| | 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__32} | Release | 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__38} | Release | Release notes | |-|-| | 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__44} | Release | Release notes | |-|-| | 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__50} | Release | Release notes | |-|-| | 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__56} | Release | Release notes | |-|-| | 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__62} | Release | Release notes | |-|-| | 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. | [ ]