Pick what to transfer by file type and condition
Files written into the same folder often belong on different servers, depending on type, filename or size. In INNORIX Studio, build a Flow and a file filter per target server so CSV goes to the data processing server and PDF to the document archive. Nobody has to open files and sort them: each Flow selects only the files that are its own and transfers those.
Comment c'est construit
- Decide the sorting rule and the receiving servers.
Decide, for example, that
*.csvgoes to the data processing server and*.pdfto the document archive. Confirm that the conditions you intend to use — filename rules, extension, size — match the real files. - Connect the source and target devices in Devices.
Register the shared source server where the files are created and both receiving servers, and confirm each storage path is reachable.
- Set the CSV condition on the first Flow.
Point it at the shared source folder, filter it to include CSV only, and set the data processing server as the target.
- Set the PDF condition on the second Flow.
Use the same source folder, include PDF only, and set the document archive as the target. If it should run on its own, set a supported schedule or event condition on each of the two Flows.
- Verify the sorting and transfer with a mixed set of files.
Test with CSV, PDF and a temporary file that should be excluded in the source folder. In Runs, check which files each Flow selected and whether it completed, and verify that only the intended type reached each target folder.
Où c'est utilisé
- Splitting ERP output by business function
From one output folder, order CSVs go to the order processing server and tax invoice PDFs to the document archive, so each downstream system receives only what it needs.
- Separating factory production data from quality documents
Production CSVs go to the analysis server and inspection report PDFs to the quality management server. Useful when files from the same source device have different owners.
- Sorting video production output
Master video files and the smaller review images and documents are separated by extension or naming rule and sent to different working servers. Verify the filter conditions and file size ranges actually supported.
- Branching data pipeline inputs
Parquet and CSV files for analysis go to the data processing server while result reports go to a separate reporting server, splitting the follow-on work by file type.
- Automating internal delivery of partner files
Order files and contract documents gathered on the external SFTP receiving server go to the internal business server and the document server respectively. The external SFTP receipt itself can stay as it is.
- Separating what gets backed up
Large archive files and operational logs go to different storage devices, keeping their retention policies apart. This is not presented as a replacement for a full backup retention and recovery policy.
- Excluding temporary and unwanted files
In-progress files such as
.tmpand.partare excluded so only finished output is transferred and downstream systems never receive a partial file. Verify what counts as finished together with how the source application saves.
Guides d'utilisation
Questions fréquentes
Is there a solution that sends files to different servers based on their extension?
In INNORIX you connect the source and target devices and then set include and exclude conditions per Flow. A Flow that selects CSV can go to the analysis server while a Flow that selects PDF goes to the document server, which is how conditional transfer is built.
Can CSV, PDF and image files mixed in one folder be sorted and transferred automatically?
Supported filters on extension, filename and the like can separate what gets transferred. This is not the same as AI classification that reads and understands file content, so documents that extension alone cannot tell apart may need a separate sorting step.
Can the target depend on file size or a filename pattern?
INNORIX file conditions can use filters such as extension, include and exclude, regular expressions and size. Check and test the filter syntax your version provides, how conditions combine, and which of them apply to each Flow.
Can one Flow branch to several destinations by condition?
This guide uses the approach of a separate Flow per target, each with its own conditions. Whether a condition-branching UI exists inside a single Flow has to be checked per product version, and nothing here is built on a feature whose support is unconfirmed.
When a new file is created, can it go straight to the server its conditions point to?
Where the environment supports file creation events, each Flow can be set to run on the event so a new file transfers as soon as it arrives. Detection while a file is still being written, duplicate events and several Flows running at once all need verifying in your own environment.
If one file matches several conditions, is it transferred more than once?
When the file conditions of different Flows overlap, the same file can go to more than one target. To avoid duplication you did not intend, make the include and exclude conditions mutually exclusive and confirm with test files.
What happens to files that match no condition?
A file that does not match the filter is simply left out of that Flow. Do not assume it is deleted automatically or moved to another server. Handling unsorted files needs its own Flow or an operational procedure.
Can the results of conditional transfers be reviewed centrally?
Runs in INNORIX Studio shows the run status and result of each Flow. Naming Flows after their conditions makes it easier for an operator to see which kind of file went to which target. Successful handling by the receiving application has to be confirmed separately.