Testing configurations with Sandbox
Build, test, and promote configuration changes without affecting your production.
As your Atomicwork setup grows — new workflows, an updated SLA, revised service catalog items — configurations become interconnected. An update to one workflow might affect how another routes requests. A change to an SLA policy might interact with escalation rules established earlier. The more sophisticated your setup, the harder it is to anticipate every downstream effect of a change.
You can now test your configuration changes in Sandbox before taking it live to production. This gives you an isolated environment that mirrors your production configuration, so you can build, test, and perfect your workflows before they go live. When you're confident everything works, you selectively promote changes back to production — with full visibility into what changed and where conflicts exist.
How Sandbox works
When you create a Sandbox, Atomicwork provisions a separate environment linked to your production account. This environment clones your existing configurations so you can experiment freely without affecting live data or workflows. The following configurations are cloned from production to sandbox:
At the account-level
-
Workspaces
-
Assistant settings