Dynamic Properties
A pipeline can define the workflow of a file through a sequence of actions. A particular file is unknown until the pipeline is deployed and executed. However, the pipeline definition must somehow refer to the file being processed generically. To do this, Centro pipelines use dynamic properties.
A dynamic property passes information about the file that the current job has found from trigger to actions. You can extract the file name, file path, file extension, and time and date stamps to build a string.
For an action field, such as the CAD Filepath, the actual file path and file name will differ depending on the file that's queued; however, the pipeline action must describe this generically to accommodate these dynamics.
When an action field contains the dynamic property icon, you can click on the icon to see the list of dynamic properties available for that field. Typing a percent sign (%) will also display the list.
Examples
Directory watcher name: DirWatcherName
Source file path: C:\CADFiles
Queued file name: test.step
Dynamic String | Resulting Output |
|---|---|
CODE
| C:\CADFiles\test.step |
%DirWatcherName.dw_changed_dir%\outputFile_%DirWatcherName.dw_file_extension%.ACT3D | C:\CADFiles\outputFile.step.ACT3D |
%DirWatcherName.relative_path%\%DirWatcherName.dw_filename_extension%.ACT3D | C:\CADFiles\test.ACT3D |
The file that changed or was added with full path and extension
The absolute file path and file name of the file queued.
Dynamic Property code | %DW_Name.dw_changed_file% |
Result example | C:\CADFiles\test.step |
The directory of the file that changed or was added
The absolute file path of the file queued.
Dynamic Property code | %DW_Name.dw_changed_dir% |
Result example | C:\CADFiles |
The name of the file that changed or was added without file extension
The file name of the file queued without the extension.
Dynamic Property code | %DW_Name.dw_filename% |
Result example | test |
The extension of the file that changed or was added
The extension of the file name of the file queued.
Dynamic Property code | %DW_Name.dw_file_extension% |
Result example | step |
The name of the file that changed or was added with file extension
The file name and extension of the file name of the file queued.
Dynamic Property code | %DW_Name.dw_filename_extension% |
Result example | test.step |
The relative path of the file from the watched directory
The relative file path of the file name of the file queued.
Dynamic Property code | %DW_Name.relative_path% |
Result example | C:\CADFiles |
Auto-incremented file version
An auto-incremented, sequential, numeric value. This can be used to give a unique number to files being processed.
Dynamic Property code | %DW_Name.incremented% |
Result examples | First job - 1 Second job - 2 |
The relative URL of the uploaded Catalog Resource
The identifier of the Catalog part created.
Dynamic Property code | %CAD_to_Catalog_1.catalog_id% |
Result example | "seascooter" |
Datestamp
The server based date in the format of yyyy-mm-dd. This can be used to give a unique number to files being processed.
Dynamic Property code | %CentroGlobal.Dateestamp% |
Result examples | 2016-02-20 |
Pipeline-wide counter
A counter value for the pipeline. This can be used to give a unique number to files being processed.
Dynamic Property code | %CentroGlobal.NthPerPipeline% |
Result examples | 1 |
Globally unique JobID
A counter value for the pipeline. This can be used to give a unique number to files being processed.
Dynamic Property code | %CentroGlobal.GlobalID% |
Result examples | {14975117603}-{214} |
Timestamp
The server based time in the format of hh-mm-ss-mmm. This can be used to give a unique number to files being processed.
Dynamic Property code | %CentroGlobal.Timestamp% |
Result examples | 09-24-22-427 |
Job-wide counter
A counter value for the job. This can be used to give a unique number to files being processed.
Dynamic Property code | %CentroGlobal.NthPerJob% |
Result examples | 214 |