Background: Transactional data in Webmail/Workflow is tiny, not requiring much disk space; however, the file transfer data (the actual files) is very large. It is important to manage how and where this data is stored.
Problem: You have multiple locations and you want to control where the files are stored when being sent via Webmail or Workflow. For example, a single FTP/FC server located in New York will typically force a user located in your London office to always upload files to the New York server. This might not be an ideal scenario, particularly if the ultimate destination is meant to also be London.
Solution: Install a new FC or FTP server in London. Log into Webmail/Workflow as Super Admin, go to “Modify Configuration”, and click on FC Servers to add the new server to the list of defined FC/FTP servers in Webmail/Workflow. With more then one FC/FTP server defined (in our example, New York and London), you will be able to assign users, groups and order forms to a specifc FC/FTP server. You may also add a drop down to the form to let users select from their available servers.
Visit this article on our blog to see an even more in-depth implementation: go further with multiple servers
So what happens if you don’t have multiple office locations but you still wish to segregate your storage by department or project for example.
You can use the same feature and just create 2 FTP/FC accounts on the same FTP/FC server and define these as 2 different FC/FTP Servers in Webmail/Workflow. Each FTP/FC account could be pointing to a different path on your storage. This will allow you to have fine grain control on which user, group or order form can access which path on your storage. In Workflow you can also control the exact path where you want the files to be dropped. By default, all the files will be stored in /fcweb/<USERNAME>/<JOBID> but this path can be changed with static and dynamic values. You can take any text value from the from the form, user or system to create your own target path for the files.