Below is how Pre and Post run configuration looks like. You can write and store VB/Java scripts in Pre-Run iScript tab and Post-Run iScript tab. Scripts stored inside iScript tabs will be saved inside your Process file and will always be available.
You can individually set either pre-run or post-run process or both.
If you want any external process to run BEFORE regular Process Runner task, you can that set by checking “Pre-Run Process Settings” box. Similarly if you want any external process to run AFTER regular Process Runner task, you can set by checking “Post-Run Process Settings” box.
External process could be an externally stored Executable (.EXE), Batch (.BAT), Visual Basic scripts (.VBS), Java Scripts (.JS) or internally stored Visual Basic or Java scripts. Internally stored scripts are known as iScripts.
For execution flow setting for controlling process runner task run when external process is busy or terminated. The settings are:
1.Wait options: This setting is done when you want process runner task to wait or continue without waiting for external process to terminate.Options are as follow:
•1-No Wait: By setting this, the Process Runner task will not wait for the external process to finish and proceed.
•2-Wait until terminated: By setting this, the Process Runner task waits till the external process finishes completely.
•3-Wait until second: By setting this, the Process Runner tasks wait for that many seconds given and then proceed . If the external process finishes by that time, the exit code is trapped else ignored.
2.Stop on error: When you check this box, the Process Runner task stops as the external process return error exit code(non zero). This box is disabled when you select “1-No Wait” as wait option.
Next is external file, you can select file that you want to execute as well as pass necessary parameters to that file as follows:
1.Select File: Here you can choose file you wish to run before/after Process Runner task. You can choose from .Exe, .Bat, .VBS or .JS file.
2.Parameters: If the external file requires any command line parameters, you can provide them here. You can also choose standard parameters for the context menu there or by clicking ellipse at the end of the text box to get list. Each parameters must be separated by comma.
If process type is transaction (TX), you can also control behavior for additional run types as follows: 1.Run with normal run: The process will be executed in normal run mode. 2.Test Run: The process will be executed in Test Run mode also. 3.Run with Debug: The process will be executed in Run – Debug All and Run – Debug Error mode also. 4.Run with Error Processing: The process will be executed in Error Processing Run mode also. |