Let's extend our first example by illustrating how a job can be made to take different execution paths based on what happens during the running of the job.
In the previous example we configured an OnSubjobOK example, but what if the subjob did not work as expected? The Studio also offers another subjob connector—OnSubjobError—for this situation. Let's modify the job to show this; perform the following steps:
messagein the Palette window and drop a tMsgBox component onto the designer.
Something Went Wrong!!.