The Upload process

The first thing the script client does is validate that the specified Job exists for this particular organisation. If the job is located, the packing slip is downloaded and saved in the log directory. This packing slip is then used to determine if the specified files to upload are allowed.

The script client will first try to locate every file specified for uploading. If the file is not found an error is recorded and processing continues to the next file listed for uploading.

For each file, the script client validates that its size falls within the minimum, maximum file size allowed for files uploaded to this job. This size is specified when the job is created and it can be changed by going to the Job maintenance window and modifying the minimum and maximum file sizes in the relevant input fields.

If the Job had some associated files, the script client validates that the files listed for uploading to the script client are in the associated files list for the job. Only those files that are listed in the associated files list are permitted.

If the Job has an associated file count, then the transfer is automatically marked complete when this number of files has been uploaded to this job. Attempting to upload more files to this job results in an error being written to the logs for each extra file attempting to upload after this point.

If the Job specified is a manual job, the transfer will be marked complete after all files to upload have been processed successfully. If an error occurred with any of the listed files for upload, then the transfer will not be marked as complete. To force a manual completion, run the script-client with an empty file list, for example, specify -l " " on the command line.