A Sandbox is a copy of the Sage People production org in a separate environment. It's isolated from the production org. You'll typically use it for developing new functionality, testing, and training, without compromising data and processes.
There's more than one type of sandbox. The full sandbox is the most commonly used type in Sage People implementations. We can periodically refresh Sandboxes; a refresh takes a fresh copy of the production org and writes it to the sandbox. You can refresh different sandbox types at different intervals. Wait until the refresh interval has elapsed before you refresh again.
Full Sandbox
You'll use full sandboxes as testing environments. They're the ideal sandbox type for most Sage People implementations. A full sandbox is the only sandbox type to support performance testing, load testing, and staging. It replicates a production org, complete with configuration (metadata), and all data, such as object records and attachments. The 29-day refresh interval means it's impractical to use full sandboxes for development as users usually need a much more frequent refresh.
Other Sandbox Types
-
Developer
Intended for coding and testing in an isolated environment. A developer sandbox includes a copy of the production org configuration (metadata). The developer sandbox refresh interval is one day
-
Developer Pro
Intended for coding and testing in an isolated environment. A developer pro sandbox includes a copy of the production org configuration (metadata). It offers a larger storage limit than Developer sandboxes. This allows more robust test data sets and more extensive development and quality assurance tasks. The developer pro sandbox refresh interval is one day
-
Partial Copy
Intended for use as testing environments, typically to enable user acceptance testing, integration testing, and training. A partial copy sandbox includes a copy of the production org configuration (metadata) and a subset of production data. We define this with a sandbox template. The partial copy sandbox refresh interval is five days
Metadata is data about data. It includes things like configurations, code, automation logic, and page layouts. This is the data defining how objects and their records behave, and the appearance of your org. Metadata refers to Salesforce configuration, rather than Salesforce data.
Advantages of using Sandboxes
A sandbox environment enables an HR team to:
-
Add new or amend existing configuration and test thoroughly. Only when satisfied with performance and operation introduce the changes to the production environment
-
It provides a safe environment for new HR team members to practice with system fundamentals while not corrupting any data
Key facts
-
To get a sandbox for your Sage People org, contact you Customer Success team or the Sage People support team. Your org comes with a fixed number of available sandbox licenses. If a license is available for the type of sandbox you want, Sage People builds the sandbox for you
-
Sandbox creation takes a minimum of a few hours. The time it takes depends on the size of the org and the workload on the Salesforce servers hosting the org. Sage People notifies you when we've created the sandbox
-
To log in to a sandbox:
-
Use the url: https://test.salesforce.com
-
Use your production username and append the name of the sandbox
For example, your username for the production org is [email protected]. The name of the sandbox is FullSndbox and your username for the sandbox is [email protected]
-
Use the password associated with your production username. To request a password reset, contact your Customer Success Manager or raise a Sage People support request. You can also initiate a password reset by clicking Forgot your password from the log in page
-
-
To request a sandbox refresh, raise a Sage People support request. The support team confirms you're not testing the sandbox and that they can overwrite with data from the current production org