Use this link to download the Process File Example files.
Unpack the zip file in the JobScheudler live folder, where you will find a job chain and an order as well as a dummy job that symbolises the file processing.
The example order will start at 12:30. This can be changed as required and can be made cyclic if required.
The "trick" lies in the ExistsFile job, which checks whether a file is present. If the file is not present then this job will be restarted every minute up to a maximum of 30 times. If no file is found the order will then end in error. If a file is found, the job chain will continue to be processed.
This "polling" effect is realised using "setbacks". This is defined at for the job and for the job chain.
From our point of view, this is the simplest solution.
As the ExistsFile job can also start job chains, this can be carried out in two steps - which is perhaps better for testing.
- First of all a job chain, which only consists of the ExistsFile job and then
- a second job chain, which is started by the ExistsFile job, as soon as a file (or all files) are found. An order can then be started for each file: these orders then being carried out in parallel if required.