RelativityOne Sandbox

RelativityOne Sandbox refers to reusable RelativityOne environments that allow you to test SQL scripts, event handlers, API based applications, custom pages, and custom agents for both the current and Early Access (EA) release of Relativity.

Note: Sandbox is a service that you must subscribe to. Please contact your Account Manager for more details.

Both sandbox instances (e.g., current and EA) will be upgraded month-to-month. Your users will have a unified login between their production instance and their Sandbox instance and be able to switch between instances easily.

This page contains the following information:

Accessing Sandbox environments

Considerations for access to RelativityOne Sandbox includes the following:

RelativityOne Sandbox contains the following two environments:

Instance URL for the new environments will be formatted as follows:

Granting users access to your Sandbox

To grant users access to Sandbox instances:

  1. In your production instance, associate the "Sandbox Auth Provider" OpenID Connect login method to each relevant user account (with the email as the OpenID Connect Subject).
    1. Navigate to the User and Group Management > Users tab.
    2. Search for a relevant user, and then click on their name.
    3. Copy the user's email address.
    4. Under the Login Method (User) section for the user, click New.
    5. Under the Provider dropdown, choose Sandbox.
    6. In the OpenID Connect Subject field, paste the email address for the user.
    7. Save your changes and repeat the process for each user to whom you need to grant access.
  2. Associate each user from the previous step to the Sandbox system group in your production Relativity instance to grant them access to your Sandbox environments.
  3. The group of users that is synced to your Sandbox instance will be named User Sync from <DNS> (e.g., User Sync from Acme). Any new users that are synced over will have email addresses set to a random generated number format (e.g., 5568986@6A51837F32B74DED85C420FD031409DA.com). Existing users in Sandbox will not be modified.

  4. Once you have done this for all the users you want to provide Sandbox access to, navigate to the User and Group Management > User Sync Preview Information (Master) tab and review what's shown.
  5. After about 5 minutes or so, the users being synced over should have a status of "Created" in the Created column of the Users drop-down table.

  6. Navigate to each of the sandboxes (EA and Current), and perform the following steps to assign the proper security permissions in each of the sandboxes.
    1. Navigate to the User and Group Management > Users tab.
    2. Add each new user to the System Admin group or other security group you’d like them to have access to (similar to your main instance).

Removing a user from your Sandbox

To remove a user from your Sandbox:

  1. Remove the user from the Sandbox group on your master instance(s) to ensure that it wont be synchronized again.
  2. Delete or inactivate the user in your Sandbox environment.

Upgrades of your Sandbox environments

Refer to the following considerations for Sandbox upgrades

Note: If there is a new Windows update available to apply, your system will automatically reboot and apply the updates outside of local business hours (2 am).

Sandbox upgrade cadence calendar

The following calendar shows the planned Sandbox upgrade cadence. The exact dates of upgrades may vary. The start date of an upgrade event in the calendar is the first possible date that the upgrade may occur. Please refer to Sandbox extended downtime windows for more information on these upgrade dates where system downtime may occur.

Legend
Production environment events
Current Sandbox events
EA Sandbox events
Date ranges where the current Sandbox will not match your production environment are shown with a red background.

Sandbox extended downtime windows

Troubleshooting considerations for Sandbox

For Sandbox, the application logs are written to the EDDSLogging database and the Tenant Reporting account has read-only access. In RelativityOne production, read access to this database is not available and you must work with Relativity Support if help with troubleshooting is required.

Differences between production and Sandbox environments

Infrastructure

Sandbox environments do not contain the same infrastructure as your RelativityOne production instance; each instance is a very scaled down version of a Relativity instance.

Relativity components

The following Relativity components will be untestable in your Sandbox:

Note: Visual Studio Remote Debugging is not currently allowed in Sandbox environments.

Sandbox Support policies

Sandbox environments do not have the same service level agreements as RelativityOne production instances.

Sandbox environments are considered 2nd tier environments. Issues with your primary RelativityOne production instances will always take precedence over a similar issue in a Sandbox environment. Furthermore, there is no such thing as a catastrophic or NIA incident for these environments. Response speed will be based on the relevant Relativity team handling the issue and their availability. Additionally, Relativity does not offer performance support for Sandbox environments (as noted in the Infrastructure section).

Data in Sandbox environments

Consider the following:

Community Updates

Aero Developer FAQ Evolving the Platform Most recent release notes
Learn more Learn more Learn more

Additional Resources

   
Access Third-Party Tools with GitHub     Create .NET Apps Faster with NuGet
Visit github     visit nuget