Run Visual Workflows
The run menu gives you several ways to execute the same visual workflow.
Run
Use Run when the workflow already contains everything it needs.
This is best for workflows that:
- Log in to a vault.
- Search for files.
- Work from the current vault folder.
- Do not depend on selected files or CSV input.
Run With Selected Files
Use a selected-file run option when the workflow should repeat file-specific actions for the files or folders you choose.
PDMShell keeps the most recent selected file runs in the Recent files menu so you can rerun the same workflow against a recently used file path without browsing again.
This is useful when the workflow uses placeholders such as:
$fileName$filePath$folderName$folderPath$revision$version
Each selected item provides its own context while the workflow runs.
From 4.0.94, Browse to Folder accepts multiple folders in one selection. Use Ctrl-click for separate folders or Shift-click for a range in the picker. Cancelling the picker runs nothing. This applies to the top Run menu and the matching action context-menu run options.
Run With A Search Favorite
Use a search favorite when a saved PDM search should provide the files for the workflow.
This is useful for repeatable jobs such as:
- Processing all files returned by a saved engineering search.
- Running a cleanup workflow against a known search favorite.
- Applying the same workflow to a controlled list of matching files.
Run With CSV Input
Use CSV input when the workflow should run against paths listed in a file.
This is useful for migration, cleanup, reporting, or batch automation where the list of files is prepared outside PDMShell.
Run from an action (4.0.92)
Note
Available in PDMShell 4.0.92 and newer.
Right-click an action and choose Run from here to run it and the remaining workflow, or Run this action only to test one action. Both submenus use the same colors, icons and target choices as the top Run menu: normal Run, Browse to File(s), Browse to Folder, Search Favorite, CSV of File Paths and Recent files. The toolbar keyboard shortcuts still run the full script.
Review the confirmation before continuing. Earlier actions are skipped, so the current session must already have any required login, folder and variables. Commands can change real files or vault data; this is not a dry run. The editor's complete script and saved vault script are not replaced or saved by a partial run.
If the action belongs to an IF/Else block, the confirmation explains that the complete containing block will run to preserve its conditions. Scripts with UNTIL or explicit jumps must use the top Run menu; partial runs refuse them because their targets may lie outside the selection.
Cancelling the confirmation runs nothing. Normal target selection, license/permission checks and Stop behavior still apply.
These captures show the actual 4.0.92 menu controls with synthetic test data; no vault commands were executed.
Choosing The Right Run Option
| Situation | Recommended option |
|---|---|
| The workflow is self-contained | Run |
| The workflow depends on selected files or folders | Run with selected files |
| The workflow should use a saved PDM search | Run with a search favorite |
| The workflow should use a prepared file list | Run with CSV input |