¶ Description
Compute the next file version number.
¶ Parameters
¶ Parameters tab
Parameters:
- Name of the Global Parameter The name of the global parameter where the detected version number will be stored. This value can be referenced in other actions via parameter expressions (e.g.,
{{MyVersion}}). - File Filter for files to versionize A file path and name filter (supporting
*wildcards) used to locate all relevant versioned files. The action expects filenames to include a numeric version component (e.g.,out_v1.txt,out_v12.txt).
¶ Description tab
Parameters:
- Script name
- Short description
- Revision
- Decription
¶ Configuration tab
See dedicated page for more information.
¶ About
The versionPlusPlus action is used to manage file versioning by automatically determining the highest versioned file in a given directory and storing that version number into a global parameter.
This is particularly helpful in pipelines that generate or process versioned files (e.g., report_v1.txt, report_v2.txt, etc.). By identifying the latest version dynamically, this action enables automated version tracking and reuse without hardcoding version numbers.
It scans the filesystem using a provided filename pattern with wildcards, extracts the numeric portion from matching filenames, and assigns the maximum version value found to a user-defined global parameter.
This action provides a simple yet powerful mechanism for automating version tracking in data processing workflows. For example, if your pipeline generates files like out_v1.txt, out_v2.txt, ..., out_v7.txt, the versionPlusPlus action will scan the directory, detect out_v7.txt as the most recent version, extract 7, and assign it to the specified global parameter (MyVersion).
The stored version can then be:
- Used in naming outputs (e.g., out_v{{MyVersion + 1}}.txt)
- Referenced for conditional logic
- Logged for audit or monitoring purposes
This versioning logic is ideal for pipelines that:
- Process daily/weekly files
- Append or rotate backups
- Track incremental outputs
