Table of Contents

Edit Command Settings

When you select an action, the command details area shows the settings for that command.

The Command Parameters panel and its divider are hidden when no command box is selected. Select a command to reveal its parameters; clear the selection to give the space back to the visual grid. The panel remembers its resized width. Standalone and vault script documents use the same main editor.

PDMShell 4.0.94 workflow and Command Parameters panel

The details area includes:

  • A visual name for the action.
  • Command settings such as filePath, search, recursive, and command-specific options.
  • A short description for the selected setting.
  • Browse buttons for file and folder settings when available.

Visual Name

The visual name is the text shown on the action in the workflow.

Use short names that explain the step:

  • Find PDFs
  • Check out files
  • Set revision
  • Notify user

The visual name is only for readability. PDMShell still uses the real command and command settings when it runs the workflow.

In 4.0.94 and newer, double-click an action on the canvas to rename it directly. Press Enter or click away to save, or Escape to cancel. Clearing the name restores the command's default label. The Visual Name property stays in sync, and a changed name marks the document as unsaved.

Editing an action name directly on the canvas

Actual 4.0.94 editor controls with sample data. The name is stored in the document's visual metadata, not in the executable command text.

Visual names are saved with standalone and vault script documents. Copying only executable script text does not carry custom names or positions. An IF action's visual name is separate from its executable Handler name.

Command Settings

Command settings map to the same parameters used in the command reference.

For example, a checkout action may need either:

  • filePath for one file.
  • search for matching files.

Some commands also support optional settings such as recursive, columns, comment, or csv.

Browse Buttons

Some settings include a browse button. Use it to select files, folders, scripts, or other values without typing the full path manually.

Validation

The Visual Code Editor validates actions while you build the workflow.

Visual command validation

If a required setting is missing or two settings cannot be used together, the action shows a warning or error. Select the action to review the message and correct the settings.

For example, checkout requires either filePath or search. If neither is set, the editor reports:

Specify either -filePath or -search.

Validation helps catch common mistakes before the workflow runs.

Edit this page