Skip to main content
Share / Export

TEDI Initial Setup

Complete this setup once on the Vista workstation that will run TEDI. When you finish, the Windows Service is running, your license is active, and the local Vista catalog is loaded so automations can resolve forms and fields.

Who should do this​

  • The person installing TEDI on a Vista workstation.
  • Someone with a TEDI license key and SQL credentials (or Windows auth) for the Vista database.
  • Someone who can confirm the TEDI Windows Service is Running after install.

Before you start​

  • TEDI is installed and the desktop app opens.
  • The TEDI Windows Service (display name TEDI Runner) is running.
  • You have your license key (you may have entered it during setup registration).
  • You know the SQL Server name, database name, and how you authenticate (SQL login or Windows integrated).
  • ODBC Driver 17 or 18 for SQL Server (x64) is installed.

Step 1: Confirm the Windows Service​

  1. Open Windows Services (services.msc).
  2. Find TEDI / TEDI Runner.
  3. Confirm Status is Running and Startup Type is Automatic.
  4. If it is stopped, start it, wait a few seconds, then continue.

Expected outcome: The service is Running. Scheduled automations depend on this service—not on the desktop window staying open.

Windows Services showing TEDI Runner service Running with Automatic startup

Step 2: Activate your license​

If you entered a key during install, TEDI may already show an active license on first launch. Still verify it in Settings.

  1. Open Settings.
  2. Select the License tab.
  3. Review License Status for Status, Plan, and Valid until.
  4. If you see No license activated, enter your License key in Activate License and select Activate.
  5. Optionally select Verify license to refresh status from tuds.ai.

Expected outcome: License Status shows an active Status, Plan, and Valid until. Command Center License metric updates accordingly.

Settings with License tab selected showing License Status and Activate License panels

Activate License panel with License key field and Activate button

License notes​

  • An inactive or missing license blocks scheduling and automation.
  • Your plan may limit how many playbooks can be active (for example, Standard vs Professional).
  • Validation runs against tuds.ai — the machine needs outbound network access for Activate / Verify.

Step 3: Connect Vista SQL Server and refresh the catalog​

TEDI keeps a local metadata catalog of Vista forms and fields. Automations use that catalog when opening programs. Without a successful refresh, the library may be empty or runs may fail early.

  1. In Settings, select the Database tab.
  2. Read the status line. If you see Catalog not loaded — save your connection settings and refresh from SQL Server, continue below.
  3. Fill in:
  • Server — SQL Server host or instance (placeholder style host\instance).
  • Database — Vista database name.
  • Username and Password — unless you use Windows auth.
  • ODBC driver — typically ODBC Driver 18 for SQL Server (Driver 17 is also acceptable).
  • Optionally check Use Windows integrated authentication (no username/password).
  1. Select Save connection.
  2. Select Refresh catalog from SQL Server.

Expected outcome: Status shows Local Vista catalog is loaded. You should also see a last-refreshed time and a success message with catalog/form/field counts.

Settings Database tab with Server, Database, credentials, ODBC driver, Save connection, and Refresh catalog

Database status showing Local Vista catalog is loaded after a successful refresh

Database notes​

  • Use an account that can read the Vista metadata tables TEDI exports into the local catalog.
  • If refresh fails, read Last refresh failed on the Database tab, then confirm ODBC driver, server name, firewall, and credentials.
  • Re-run Refresh catalog from SQL Server after major Vista upgrades or when new forms are missing from automations.

Step 4: Set window close behavior (optional)​

  1. In Settings, select the Theme tab.
  2. Under Window Close Behavior, choose:
  • Minimize to tray (default) — Hide the window and keep the desktop app available from the tray.
  • Close — Exit the desktop app when you close the window.

Either choice leaves the TEDI Windows Service running schedules. Use Services.msc if you need to stop automation entirely.

Settings Theme tab Window Close Behavior with Minimize to tray and Close

Step 5: Return to Command Center and confirm readiness​

  1. Open Command Center.
  2. Confirm License looks active.
  3. Open Automations (or Command Center → Open automations) and confirm approved playbooks appear.
  4. Active Schedules may still be 0/0 until you create schedules—that is expected.

Expected outcome: License is healthy and the automation library lists playbooks. You are ready to queue a manual run.

Command Center after setup with License active and Automation library cards visible

Setup checklist​

  • Windows Service TEDI Running
  • License activated (Status / Plan / Valid until visible)
  • Database connection saved
  • Catalog refreshed — Local Vista catalog is loaded.
  • Automations library shows approved playbooks

Common mistakes​

  • Skipping catalog refresh — Saving connection settings alone is not enough; always Refresh catalog from SQL Server.
  • Wrong ODBC driver bitness — Use the x64 Driver 17/18 that matches TEDI.
  • Assuming closing TEDI stops jobs — The Windows Service continues; use Services.msc to stop automation.
  • Activating license without network access to tuds.ai — Activate / Verify will fail until outbound validation works.

Next steps​

  • Running a TEDI Automation — Queue your first playbook and watch step progress.
  • Scheduling TEDI Automations — Add timing rules for unattended runs.
  • Understanding Run Results and Proof Packs — Interpret Completed, Failed, and Blocked.
  • Monitoring and Troubleshooting TEDI — Service, license, catalog, and log locations.