The "Or" orchestration component waits for any of its inputs to complete before continuing the job. Once any of the inputs complete, the tasks defined after the "Or" component are added to the job. There may already be tasks in the queue however, so they may not necessarily be run next.
The input links do not have to be success links. For example, you may wish to take an action if any of a set of components fail, regardless of which particular one fails.
Only the Name property can be configured to provide a meaningful description of the component.
NOTE: Any local variables that exist in the workflow when going through the Or component will be reset to their default values. This is to prevent the need to resolve two potentially different values of a local variable when two parallel workflows meet the Or component. If this is not the case for your workflow, consider using global variables instead.
|Name||Text||The descriptive name for the component.|
In this example, if any of the loads fail we want to do some cleanup work to ensure when the job ends the database is left in a consistent state. (The details of the Cleanup job are not covered here).
The name can be set to a custom value.