Body
Impact
When the sandbox environment is refreshed, a copy of the production database will be restored to the sandbox environment, replacing the existing database. Any configuration you have done in the sandbox will be lost when that environment is refreshed.
Please note that a refresh fully clones the data (not attachments though) from production. This means that items such as links in rich HTML content (e.g. KBs, Services, Desktops, Client Portal Headers/Footers), ticketing web service configurations, Single Sign-On (SSO) configurations, outbound mail settings, and more will be the same content from production. Workflows and automation are disabled in the Sandbox as part of the copy process.
Schedule
The Sandbox is refreshed quarterly. The sandbox is refreshed from production data quarterly on the first Monday day of business of the quarter unless it is a holiday. (Q1-Jan, Q2-Apr, Q3-Jul, Q4-Oct)
IMPORTANT: Data for the refresh will be as of 11:30 PM ET the Thursday day before the refresh. For instance, if the refresh is on April 3rd, 2023, the data in the refresh will be as of 11:30 PM ET on March 30th, 2023.
Preservation of your Sandbox
If you'd like to save something from the Sandbox, you can copy things manually from Sandbox and place them in Production, like portal modules, and reports.
Objects we can copy through TD are Service, Ticket Workflow, Ticket Form, and Project Request Form.
Please open a request here.
Post-refresh Tasks for System Office Technicians
Edit the name of the Sandbox to include "Sandbox" and in the Organization Settings, change the background color of the waffle.
Change the color scheme of the TDNext Button.
