Table of Contents

Testing and troubleshooting

Test every add-in script with a small set of files before enabling it for production users.

  1. Build and test the .pdmshell script outside the add-in.
  2. Add the script in the Script Editor.
  3. Enable Always show condition test message while validating conditions.
  4. Configure permissions for a small administrator group.
  5. Enable a command menu or trigger point.
  6. Test against known files and folders.
  7. 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.
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.
PDMShell editor does not open Confirm pdmcli.exe is installed and available in the expected PDMShell installation path.
Script runs against the wrong item Check the PDM command context and whether the event supplies files, folders, or command-only data.
Edit this page