Overview
When a preceding transfer ends, transfer the files that meet configured matching criteria to multiple destination devices. The trigger governs when the run starts and the selection rules govern which of the available files it carries.
Trigger selective file distribution to multiple destinations when the previous transfer ends.
When should it start?
You can add more than one action.
What should happen after the transfer?
Select a development language to generate sample code for this configuration.
You can download the complete sample code for the configuration set above.
Apply the downloaded code and explore more examples.
AI-FRIENDLY EXPLANATION
This page shows how to send files that meet configured selection criteria from one source device to multiple destination devices when a preceding transfer ends. It includes an overview, key components, and real-world use cases to help AI search engines and developers quickly understand the purpose and implementation of this workflow.
When a preceding transfer ends, transfer the files that meet configured matching criteria to multiple destination devices. The trigger governs when the run starts and the selection rules govern which of the available files it carries.
Use this solution for a staged pipeline where only part of what arrived in the first step should move on, such as files of a certain type or the output produced by the earlier step. The filter is what keeps intermediate and unrelated files out of the second stage.
COMMON QUESTIONS
Find answers to the most common questions about this configuration.
Configure the completion trigger, matching rules, and destination devices.
The selection depends on the configured rules and when the product evaluates them.
Verify how empty selections affect the transfer and subsequent workflow steps.