Control Flow
Here we describe the definition of control flow for activities.
Not all of these options are supported for all activities! Usually, activities that do not support multi-threading (like cleanup) also do not support these options. |
Item | Meaning | Default |
---|---|---|
|
Controls whether the specified activity is executed: if set to |
For simple activities, it is |
|
Condition for processing or analysing specific buckets. (If present and if returns false, the bucket is marked as complete without any processing, and the next bucket is fetched.) |
Processing all buckets. |
|
Condition for processing specific items. (If present and if returns false, the item processing is skipped, and the next item is fetched.) |
Processing all items. |
Error handling strategy for this activity. |
Depends on specific activity. |
|
|
Whether the child activities should be executed in parallel. (This is applicable only to composite activities.) |
|
Items planned but not implemented yet:
Item | Meaning | Default |
---|---|---|
|
An expression that governs whether the current activity should be executed or skipped,
or whether the task should stop altogether. Should return a single value
of |
Pass. |
|
Set of prerequisites i.e. activities that must be complete before this one can start. |
The activity just before this one (the sequential processing). |
|
Should be the activity re-executed when the task is restarted (e.g. resumed)? |
- |