Installing and Configuring Desktop Designer

Installing and Configuring Desktop Designer - Legacy Reference

This page is retained for teams that still maintain legacy Desktop Designer assets. For new AIQ authoring, prefer current AIQ workflows and Scenario Editor where applicable.

Legacy setup guidance

• Confirm the Desktop Designer version is still required for the existing asset being maintained.
• Validate Windows version, Java/runtime dependencies, browser/driver versions, permissions, and installation path.
• Use a dedicated test machine or controlled desktop session for legacy desktop automation.
• Document any migration candidates that should move to a current AIQ workflow.
• Do not create new documentation patterns that treat Desktop Designer as the default authoring experience.

Validation workflow

1. Install or verify Desktop Designer only in the environment where the legacy test is maintained.
2. Run a small smoke test and capture evidence.
3. Record compatibility issues, required permissions, and migration follow-up.

Legacy note: Keep this article only as a legacy reference until older Desktop Designer content is consolidated or retired.

Last updated: October 10, 2026