One feature of MOVEit Transfer that is not routinely used is Webposts; these are forms that you can set up for people to input information to be passed into MOVEit. This information is placed into a subfolder under the Webposts folders and can be accessed as xml.
There are many ways that this function can be used in an organisation, however, in this article we are going to look at using it as the basis for a file transfer approval system.
This needs us to have MOVEit Transfer and MOVEit Automation; Automation needs to have custom scripts licenced.
The scenario that it will address is this: An end user wants to move files from a folder that he has access to into a folder that he has no access to. The steps that make up this process are as follows:
In the Transfer server, add the following folder structures with files. A basic web.config file can be added to each folder:
Two new virtual folders named ‘Approvals’ and ‘Posting’ need to be created, pointing to the relevant folders above.
You now need to create the webpost forms. Index.html is the initial form that the end user will complete, and template.html is similar but with an approval button. Template.html has all entries prefilled with dummy values that can be easily replaced, e.g. in the source field a default value of ‘ZZZSourceZZZ’ is used. My index.html looks like this.
In the Transfer web UI, you need to create a couple of folders under the webposts folder, I named mine Approvals and Requests.
When you have finished this part, you should be able to navigate to https://<your_transfer_url>/posting and see the approval request form, looking something like this:
If you complete the form, you should get a success message:
However, the xml will remain in the webposts/requests folder until the Automation setup is completed.
You need two custom scripts to run in the Automation tasks:
Finally, there are four tasks required to handle the process.
This task (step 2 in the list above) downloads the xml created when a user submits the form, and reads the content. It then passes this information to the next task in the flow as parameters:
In the second task, we take a copy of the template and update it with the parameters passed from the previous task. The result is saved as a new webform template with a random name into the posting folder and the selected approver receives an email with a link to it.
The third task is triggered by the approver completing the webpost approval form. It’s the only advanced task used:
We again read the xml generated by the webpost, which this time also includes the yes/no for the approval. If this was a yes, the final task will be launched with parameters being passed to it:
This is the final step of the process and literally copies the content from one directory to another.
In this example, you can see that both directories are on the same server (Transfer), however, there is no reason not to put them on any other protocol (SFTP, FTP, UNC) as the situation requires.
Finally, I should mention that the webposts are anonymous. Because of this, it makes sense to host the forms on a server that is not being published to the internet, or risk being flooded with bogus forms. Alternatively, you could introduce some form of validation and discard entries that don’t meet your criteria
We'll also be able to supply you with various components in text format. Our Technical experts have years of experience in the MFT industry and work with MOVEit on a daily basis.
For more support on creating a file transfer process request in MOVEit, please get in touch with us.