Sandbox Database for Beta Testing

Overview

Before rolling out new Tascus features or beta versions to your live production line, it's good practice to test them in an isolated sandbox environment first. This article explains why, and walks through how to set one up so your Manufacturing Engineers (MEs) can trial beta functionality without any risk to live production data.

Why Use a Sandbox

• Zero risk to production — the sandbox runs on a completely separate Tascus database, so nothing tested there can affect live routing, orders, or traceability records.

• Realistic testing — MEs can trial new sequences, BoM changes, or beta features on real workflows before they go live.

• Simple to maintain — a single laptop dedicated to the test database means no per-session reconfiguration; it's always pointed at the sandbox.

How It Works

A fresh Tascus install locates its database using a local configuration file:

C:\ProgramData\Tascus\data\Data Storage Settings.xml

This file stores the database connection details (location and authentication). Repointing a machine to a different database — live or test — means changing this file, either by editing it directly or via the in-app Settings > Data Storage screen.

User logins are also stored within the Tascus database itself (Users table). This means:

• Logins are not shared between your live and test databases.

• A shared ME login created on the test database will not work on your live Tascus and vice versa.

• You only need to create the shared ME login once, on the test database.

Recommended Setup

1. Provision a test database on your server (Metis can assist with this — same process as your live database, just a separate instance/schema).

2. Dedicate a laptop to the sandbox. Any laptop the MEs already have access to works — this avoids needing to reconfigure a shared machine every time someone wants to test.

3. Point that laptop at the test database via Settings > Data Storage in Tascus (or by editing Data Storage Settings.xml directly if doing this via IT/imaging).

4. Create a shared ME login on the test database (e.g. ME_Test). Since this login only exists on the test database, there's no risk of it being used — accidentally or otherwise — to log into live Tascus.

5. Leave the laptop configured this way — it becomes your permanent sandbox terminal for trialling beta releases.

Common Questions

Can multiple users share one login on the test database? Yes — since it's isolated from live, a shared login is a reasonable simplification for test purposes.

Will the shared test login work on our live Tascus? No. Logins are database-specific, so a test-database login has no access to the live database.

Do we need to do anything to our live database for this to work? No — the live database and setup are unaffected. This is purely an additional, separate database and a laptop configuration change.