Developer Sandboxes

If you have permission, you can allocate and retire the sandboxes you've created in your instance.

Allocate sandboxes to your development teams so they can start using them for development.

Use source control with Developer Sandboxes to enable parallel development and help avoid merge conflicts.

You should understand how plugins and sandboxes work before you clone or upgrade an instance with Developer Sandboxes. Back up your work in a sandbox before any clone or upgrade, either by exporting the update sets or committing to source control.

Your company's entitlements determine whether you have access to Developer Sandboxes.

Follow some general guidelines to ensure you're optimizing your use of sandboxes.

To get help with Developer Sandboxes, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company. You can also check some helpful resources.

Developer Sandboxes is installed on your instance, with licenses from a pack assigned by your admin. Review prerequisites and plugin requirements before installation begins.

Each sandbox provisioned with Developer Sandboxes is an isolated environment within an instance. Developers can build and test in parallel without affecting other work.

Sandboxes use the same login credentials as the base instance, including single sign-on (SSO) when it's enabled there. Set the required properties on the base instance so developers can use SSO to access sandboxes.

Developer Sandboxes supports almost all development-related ServiceNow AI Platform features.

Developer Sandboxes installation and configuration covers Developer Sandboxes on your instance. Review entitlements, install the plugins, assign licenses, and look up the roles, tables, and properties that control how sandboxes work.

If any conkeyrefs are broken, re-add them from the doc/source/reuse/domain-separation/domain-separation-overview.dita file.In the short description, edit the first sentence to state whether domain separation is supported or not and add the application name. Keep the conkeyref at the end that describes domain separation.Domain separation is supported for Developer Sandboxes. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

Several types of components are installed with activation of Developer Sandboxes, including tables and user roles.

License assignment in App Engine Management Center (AEMC) lets Developer Sandboxes admins distribute purchased sandbox packs across non-production instances without opening a support case. Each pack contains 10 sandboxes, and assignments are managed from a license management instance.

The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively.

Developers generally have admin rights on the non-production instance where Developer Sandboxes are allocated, and can thus allocate a sandbox to themselves.

When a sandbox is ready, update set sources are automatically created on both the sandbox and the base instance, enabling transfers in either direction without manual configuration.

Developer Sandboxes provide isolated development environments that enable parallel building and testing on top of a shared development instance. Use sandboxes to reduce code conflicts, accelerate delivery, and safely test configurations without affecting other team members' work.

Retire sandboxes that are outdated or no longer needed to make room for new Developer Sandboxes in your instance.

Developer Sandboxes are isolated development environments on a shared instance. Delegated developers use them to build and merge changes in parallel, and admins request and manage them.