As said in the introduction, a Job must start with a START Job entry. All the entries that follow it are executed in a sequential way, following the direction given by the hops. Also, the execution of the destination Job entry does not begin until the Job entry that precedes it has finished.
Look at the following example:
Job with a simple flow
According to what we just said, we can deduce that:
- This Job creates a folder.
- After the folder is created, the Job copies some files (most probably to the new folder).
- When the files are copied, the jobs executes a Transformation. We can guess that this entry is for operating on the data in those copied files.
- Once the Transformation finishes, the Job sends an email.
This is the simplest flow that we can find in a Job. There are, however, several ways in which we can...
