Running a TEDI Automation

Launch a guided playbook from the Automations library, fill the launch form, queue the run, and watch step progress in Recent Runs. This is the same pattern for every approved automation.

Before you start

• Initial setup is done: license active and Local Vista catalog is loaded.
• The TEDI Windows Service is Running (needed for queued work and schedules; keep it healthy even for manual runs).
• Viewpoint Vista is installed and usable on this machine for the company you will select.
• You know the playbook-specific inputs (company, folders, batch month, close scope, and so on).

Open the Automations library

1. In the left sidebar, select Automations.
2. Optionally filter with Search (Name or module…) or Module (All modules, or a specific module such as AP).
3. Switch Card view / List view if you prefer a different layout.

Expected outcome: Approved playbooks appear as cards or rows with an Open action. Unavailable items may show Coming soon.

You can also start from Command Center → Automation library → Open automations, or use the play icon on a Command Center automation card.

Open a playbook and review the steps

1. Select Open on the playbook you want to run.
2. Read the playbook title and description.
3. Review Steps TEDI will run — the numbered list of Vista actions TEDI will attempt.

Expected outcome: You understand the sequence before you submit. Use Back to automations if you picked the wrong playbook.

Fill the launch form and queue

Launch fields come from the playbook. Common fields across many automations include:

• Goal — Short description of what this run is for (shows in Recent Runs).
• Company — Vista company TEDI should use (TEDI verifies access at start and switches companies when needed).
• Module-specific fields — for example batch month, source/archive/errors folders, close through month, or batch form.

1. Complete every required field on the form.
2. Select Queue Automation (some playbooks may use a custom submit label with the same meaning).

Expected outcome: TEDI accepts the queue request and opens the run in Recent Runs. While submitting you may see Submitting….

Watch the run

1. On the run detail, confirm status moves to In Progress.
2. Watch Current step, Progress, and the Step progress list.
3. Leave Vista alone on forms TEDI is driving while the run is In Progress.
4. When finished, status should be Completed (or Failed / Blocked if something stopped the run).

TEDI auto-refreshes the run view while a playbook is In Progress.

After a successful first run

• If a proof pack is available, select View proof pack to review the evidence summary.
• Return to Command Center — the run should appear under Recent automation runs.
• When you are ready for unattended execution, create a schedule for the same playbook.

Tips

• Start with a low-risk playbook and a test company when you are learning the product.
• Folder-based playbooks need existing Windows folders and correct permissions before you queue.
• If the library is empty, return to Settings → License and Settings → Database before troubleshooting the playbook itself.

Common mistakes

• Wrong company — Set Company on the launch form; do not assume the last Vista company is correct.
• Using Vista on the same forms mid-run — Wait until the run completes or fails.
• Missing folders or batch month — Required launch fields vary; blank paths and invalid months fail early.
• Expecting Instant completion — Longer playbooks (month end, multi-batch posting) take time; watch Step progress.

Next steps

• Understanding Run Results and Proof Packs — Failed vs Blocked, retry, and proof packs.
• Scheduling TEDI Automations — Save launch parameters on a recurrence.
• Monitoring and Troubleshooting TEDI — Command Center alerts and logs.