Collect files scattered across devices, by condition
Gather only the files you need from the many servers and factory machines they are spread across. In INNORIX Studio, define the folders on several devices as a Dataset and build a collection Flow with conditions on extension, name pattern, size and more. Instead of moving everything in the source folder, select only the files the work needs, and manage what was collected through scheduled runs and the Runs record.
- Review the source folders on each device
- Create the Dataset
- Set the file conditions
- Build the central collection Flow and its automatic run
- Confirm only matching files arrived
Guide 8 shows grouping folders across devices into one Dataset and guide 16 shows reusing a Dataset across several Flows. Guide 17 shows the result of collecting only the files that match a condition from that Dataset. A Dataset is not a store holding a central copy of the files but a logical file set referencing the source devices and paths.
How it is built
- Connect the source devices you are collecting from.
Confirm in Studio Devices that the factory, branch and research machines are connected, and check the source folder and file access permissions on each one.
- Define the scattered folders as a Dataset.
Create a new Dataset in Datasets and add the file paths across the devices. This defines what is in scope for collection; it does not move the source files to the centre.
- Set the file conditions you need.
For example, include
*.csvonly and exclude*_temp.csv, or limit the job to files in a given size range. Confirm where the conditions apply and how they are written against your actual Studio version. - Build the central collection Flow and its automatic run.
Use the Dataset as the source and the receiving path on the central server as the target. Keep a separate folder per device to prevent filename conflicts, and set a Schedule to run at a fixed time each day.
- Verify that only matching files were collected.
After a test run, check the per-device transfer results in Runs and inspect the central server for the files that should have been included. Confirm as well that the excluded files were not transferred before you put the scheduled run into production.
Where it is used
- Collecting only quality inspection results from production equipment
Of the files generated on the machines at each factory, only
QC_*.csvis gathered onto the central quality analysis server, leaving out temporary files and intermediate results. - Selective collection of closing material from several branches
From the shared folders at each branch, only the confirmed month-end reports are collected onto the finance server. Name patterns separate out the drafts and temporary files.
- Consolidating only the logs security monitoring needs
Log extensions and paths to be analysed are named across several production servers. Rather than replicating every log in production, the scope is kept to what is needed.
- Collecting large result files from research equipment
From the folders on each instrument, only result files above a given size go to the central analysis server, and the small temporary files are left where they are.
- Retrieving approved output from media production servers
From the output folders on several editing machines, only filenames carrying an approval marker or specific formats are selected and collected onto the review server.
- Automatic consolidation of partner deliverables
Of the files arriving on the receiving server for each partner, only material matching the agreed extension and naming convention is passed to the internal consolidation server. The external web upload itself is a separate INNORIX EX integration.
- Scheduled collection that leaves older files out
Where filenames carry a date, that date pattern narrows the collection scope, with storage rules set alongside it to prevent collecting the same file twice. Whether filtering directly on file modification time is available has to be checked against the product.
Usage guides
Frequently asked questions
Is there a solution that automatically collects only the matching files from several servers?
INNORIX Studio supports defining paths across several devices as a Dataset and combining file filters with a Flow to collect onto a central server. Conditions such as extension and filename pattern select only the files you need, and a Schedule runs the collection repeatedly.
Can I gather only CSV or PDF files instead of copying everything on every device?
Yes. Include and exclude conditions on extension or filename pattern can scope the job to particular file types. The exact way to enter regular expressions or size conditions has to be confirmed in the real settings screen.
Does creating a Dataset store the files from several servers centrally?
No. A Dataset is a construct that manages file paths across several devices as one logical set. The files themselves go to the central server you named when a Flow referencing the Dataset runs.
Can I collect only files whose names contain a particular word?
Filename patterns and include and exclude filters can narrow what gets collected — including files starting with QC_ and excluding files containing _temp, for example. The actual filter syntax has to be applied as your product settings require.
If files with the same name are collected from several servers, do they overwrite each other?
Using a subfolder per source device or setting a stored-filename policy reduces the risk of a conflict. Before collecting, it is worth confirming which storage rules are actually supported — overwrite, automatic numbering, date folders and so on.
Can conditional collection run automatically every day?
Yes. Set a Schedule on the collection Flow and it runs repeatedly at the time you chose. An event-driven approach that runs when a new file appears can also be configured separately, and the conditions under which the event applies have to be verified against your connected environment.
Can file size or a regular expression also decide what gets collected?
INNORIX file filter configuration includes options such as filename, extension, include and exclude, regular expressions and size conditions. The precedence when conditions combine and the exact input syntax do have to be confirmed and tested in the product version you use.
Can I see which files were not collected, or which devices failed?
Runs shows run status and failed transfers. A file that the filter conditions left out of scope in the first place is not the same as a failed transfer, though, so when testing, compare the source file list against what was actually collected.