Testing and troubleshooting
Test every add-in script with a small set of files before enabling it for production users.
Recommended test workflow
- Build and test the
.pdmshellscript outside the add-in. - Add the script in the Script Editor.
- Enable Always show condition test message while validating conditions.
- Configure permissions for a small administrator group.
- Enable a command menu or trigger point.
- Test against known files and folders.
- Expand permissions after the automation behaves as expected.
Common issues
| Symptom | What to check |
|---|---|
| Menu command does not appear | Confirm the script is enabled, Menu is enabled, command menu text is not empty, and the current user passes permissions. |
| Menu command or trigger change does not appear after saving | If the Script Editor showed the menu and hook changes prompt, restart Windows Explorer or log out and back in to the vault so PDM reloads the add-in menus and command hooks. |
| Script does not run from a trigger | Confirm the trigger point is selected and the add-in was reloaded after changing trigger configuration. |
| Conditions do not match | Enable the condition test message and verify the resolved placeholder and variable values. |
| Script runs against the wrong item | Check the PDM command context and whether the event supplies files, folders, or command-only data. |