|
<< Click to Display Table of Contents >> Navigation: Nodes > Input > Local Inputs > File Dropper |
Use this node to import file paths dropped into a remote Mistika Runner connected to the Workflows server executing this node, to pass those file paths to other nodes downstream.
To use it, create a Runner workflow as follows:
In the Workflows Creator:
- When creating your workflow include a File Dropper node to receive the file paths to be processed, and connect it to other nodes as required for your purposes.
- Save a runner workflow (File -> Save us Runner)
In the remote Mistika Runner system:
- Select the saved workflow a press Use
- Drag & Drop the desired files in the Drag and Drop panel that will appear for that purpose.
- Press Add to Queue
The workflow will be executed for each file path.
Note that what is passed is the file path, not the file itself. Then, the exact same path dropped in the remote Mistika Runner system needs to exist in the Mistika Workflows computer that is running this node (i.e having the same NFS or Samba mounts and so on...). Note that what is passed between the Mistika Runner and Mistika Workflows is only the path metadata (if you want to upload the actual file directly to a workflow then you would need to use the Received Files node and the REST-API instead)
output: Dropped file paths
recursive: If the path is a folder, pass the file paths of all the subfolders content recursively.
filenameOnly: When using the Include & Exclude properties for filtering ignore all the path folders and only match the file name.
Drag & Drop area: Placeholder to store the dropped file paths (one file path per line). You should not use this property directly, if you have a list of paths that you want to load then use the Create UPs from paths node instead.
Property Label |
Property ID |
Paths |
paths |
Recursive |
recursive |
Add Root |
addRoot |
Filter Mode |
filterMode |
File Name Only |
fileNameOnly |
Include |
include |
Exclude |
exclude |