Manual

HQ VISU Designer Troubleshooting

Start from the symptom. Check Status first, then isolate menu response, license state, export output, and script execution.

Status checkLicense and exportScript errors

Baseline

Three checks before troubleshooting

Open Status on the HQ VISU Designer ribbon and confirm the plugin version, PowerPoint version, and license state.

CHECK 1. Confirm Status

Make sure the plugin version, PowerPoint version, and license state are readable. Fix licensing first if it is unavailable.

CHECK 2. Classify the symptom

Group the issue as menu response, license state, export output, or script execution, then follow the matching section.

CHECK 3. Change one thing and retest

Adjust one setting or condition at a time, return to PowerPoint, retest, and record what changed.

Case 1

The menu does not respond or reacts slowly

Confirm the plugin is connected to the current PowerPoint session, then check licensing, initialization, and window response.

Case 2

The license is abnormal or unavailable after activation

Confirm the license mode, then check the service address, account state, offline certificate, and machine match.

Read license state from Status

If Status shows unlicensed or unavailable, handle licensing first. For online licensing, also check whether the license service is reachable.

Online license checks

Confirm the license service URL, account state, and network access. If the server revokes a license, the plugin disables related windows.

Offline license checks

The offline certificate must match the current machine and user environment. If it does not match, export a new offline request and issue a new certificate.

Generate a new offline request after changing computers
After import, check Status again and confirm the license is available
Use the production license service configuration in production

Case 3

The exported page differs, replacement is wrong, or images are stale

Confirm the export mode, then check page objects, template instances, image assets, and shared runtime assets.

Confirm full export or current-page export

Full export is for release or large changes. Current-page export is for local replacement. Use full export when shared structure, global scripts, or shared assets change.

Images or pages do not match

Decide whether the change belongs to page objects, template instances, or image assets. Re-export the current page for object changes; use full export for shared assets or structure changes.

Pre-release check

Before replacing production files, run one full export and one current-page export. Replace server files only after both outputs look correct.

Run a full export and verify the folder structure
Run a current-page export and verify the single-page replacement
Open the exported page locally before replacing server files

Case 4

A script fails or a saved configuration does not take effect

Confirm where the script is written, then check whether the field expects full JavaScript, a synchronous expression, or pure JSON.

Confirm the script location

Page script, global script, click script, and hover script can contain full JavaScript. Animation, color, and condition fields should only contain synchronous evaluable expressions.

Where fetch can be used

Use fetch in page script, global script, click script, or hover script. Move, Rotate, Scale, Script Color, and Condition should remain synchronous expressions.

Save-time errors

Confirm whether the editor expects JSON, then check callback parameters, variable scope, and valid JSON syntax.

Stable pattern

Put initialization in qteditPageReady or qteditGlobalReady. Put reusable helpers in global scripts. Prefer built-in behaviors for button actions, then extend with scripts only when needed.

Initialize in qteditPageReady / qteditGlobalReady
Keep async logic in script fields and expressions synchronous
Keep JSON fields pure JSON without var or function