File TransferUse Flux workflows to monitor your FTP, FTPS (FTP/SSL), SFTP (SSH FTP), and UNC (Universal Naming Convention), and local servers for incoming files. Your Flux workflows detect the presence of new files on your servers and then process the files individually or in one large batch, according to the design of your particular workflow.

During the execution of a workflow, you can deliver files to your FTP, FTPS (FTP/SSL), SFTP (SSH FTP), and UNC (Universal Naming Convention), and local servers.
File interaction can also be monitored for deadlines SLAs (Service Level Agreements). For instance, you can build your workflow to send out an email if files are not received by 8:00. Or if the files received are of the wrong size, your workflow could call a specialized error handler, built into Flux, which will call another workflow to handle the incorrect file size.

Create jobs that run only when certain file conditions are met. Flux can search for file dependencies on FTP, FTPS (FTP/SSL), SFTP (SSH FTP), and UNC (Universal Naming Convention) servers as well as the file system. Optionally, you can configure Flux to monitor files only during certain time periods. For example, Flux can monitor incoming files on an FTP server between the hours of 21:00 through 6:00 the next morning on business days only.
With Flux you can also make decisions on your workflow based on information about the file, such as file size, file permissions, last modified date, etc.

Flux can monitor the transfer rate and progress of file transfers. When copying files, you can see which files have successfully copied and which files have unsuccessfully copied in the Operations Console.
