Database Reference
In-Depth Information
Figure 7-16. Control flow tasks can have multiple precedence constraints arrows.
Notice that Data Flow Task 1 has two precedence constraints attached to it. Once this task completes,
control passes to both Data Flow Task 2 and Data Flow Task 3.When either one of these finishes, control passes
to Data Flow Task 4, but this can also be configured so that both tasks must complete before control is passed.
Precedence constraints can be configured to allow the execution control to flow between tasks based on success,
failure, or completion. This configuration is important because it allows you to apply conditional logic to your
design. For example, if we were to add a task that sends us an email when a portion of the package fails, we could
do so by adding a Send Mail Task, renaming it, and connecting a precedence constraint arrow from the existing
task container to the new send mail task (Figure 7-17 ). We could then configure it to execute the send mail task
only upon the condition that the previous task failed.
Figure 7-17. Setting the Constraint operation value
Although it cannot be seen in the black-and-white images of this topic, the precedence constraints are
color-coded to indicate their status. The green arrows indicate success, red indicates failure, and blue indicates
completion.
Note
 
Search WWH ::




Custom Search