Visual Code Editor
The Visual Code Editor helps you build PDMShell scripts as connected workflow steps. Instead of writing every command by hand, you can add actions, connect them in the order they should run, edit command settings, validate the workflow, and run it from PDMShell.
The workflow screenshot uses sample data in the actual 4.0.94 application controls; the example script was not executed. Older screenshots below illustrate unchanged features.
The command line is still available below the visual workspace, so experienced users can keep working with text while using the visual editor to organize longer automation workflows.
Appearance and terminal layout
PDMShell 4.0.85 follows the Windows light/dark app setting by default, including changes while it is open. Under Settings > Themes, choose Use Windows setting, Terminal Light, Terminal Dark, or Classic. Classic preserves custom console colors.
Command entry now shares the console area with output. Enter runs the command, Shift+Enter inserts a line, and Up/Down recall command history while preserving your current draft. Autocomplete initially selects its first suggestion.
Drag the horizontal divider to resize the editor and console. Click the Console header button to expand the console to the available workspace; click again to restore the default split.
Toolbar
Use the toolbar to run, stop, create, open and save scripts, and open the expression evaluator. In 4.0.80, New, Open, and Save support both standalone files and vault scripts. Scripts open in visual view first, with code view available when needed.
Vault documents show their Script settings in a resizable panel beside the canvas. Its gear button restores the panel after you close it. See Save and open scripts and Vault scripts and settings.
Code editing (4.0.94)
Use the code view button to edit the script with line numbers, syntax highlighting, and autocomplete for command names, parameters and supported values. Press Ctrl+Space to request completion. Lines beginning with # remain comments rather than executable actions.
Actual 4.0.94 editor controls with sample script text; no script was executed.
Readable mode lets you edit quoted arguments inside ${...} expressions without manually typing their surrounding command-string escape layer. Raw shows the executable representation. Copy executable script always copies that executable form, suitable for pasting into command/script consumers. Ordinary Windows path backslashes are preserved. This is an editing view, not a change to the scripting language or an evaluation of the expression.
For example, a quoted input expression appears with ordinary inner quotes in readable view, while Raw retains the escaped inner quotes needed inside a quoted command argument. Switching views does not by itself change the script. Unsupported or malformed expressions are not silently rewritten.
What you can do
- Build a workflow one action at a time.
- Search for commands by name, description, or category.
- Edit command settings from the selected action.
- Validate required settings before running the workflow.
- Run the workflow normally, against selected files, from a search favorite, or from a CSV file.
- Add IF statements and conditions so the workflow can choose between different paths.
- Save and reopen visual scripts with their visual layout restored.
Visual Code Editor Articles
| Article | Use it to |
|---|---|
| Build Visual Workflows | Learn how actions connect and how to navigate larger workflows. |
| Edit Command Settings | Understand visual names, command settings, validation, and browse buttons. |
| Run Visual Workflows | Choose the right run option for one workflow, selected files, search favorites, or CSV input. |
| Save And Open Scripts | Create, save and reopen standalone files or vault scripts in one editor. |
| IF Statements and Conditions | Branch the workflow with true and false paths. |
When To Use It
Use the Visual Code Editor when:
- You are building a multi-step PDMShell script.
- You want to validate command settings before running the script.
- You want a clearer view of how actions connect together.
- You want to reuse the same workflow with files, searches, favorites, or CSV input.
- You are helping users who prefer a visual workflow over command-line syntax.
Use the text editor or command line directly when you need quick one-line commands or already know the exact syntax.