com.coxautodata.waimak.dataflow
DataFlowAction
Related Doc:
package dataflow
The unique identifiers for the inputs to this action
The unique identifiers for the outputs to this action
Perform the action
Perform the action
the DataFlowEntities corresponding to the inputLabels
context of the flow in which this action runs
the action outputs (these must be declared in the same order as their labels in outputLabels)
For representing the action
Action has the responsibility of assessing itself and produce DataFlowActionState, that will be used by the executors to determine if they can call performAction or not.
Action has the responsibility of assessing itself and produce DataFlowActionState, that will be used by the executors to determine if they can call performAction or not. Also can be used for progress monitoring. This will allow for more custom actions without modifying the executors
- action will study the state of the inputs in order to generate self assessment
- an instance of the DataFlowActionState
Unique id of the action, but using it for adding behaviours can be problematic due to Interceptors that are defined at a much later stage.
Unique id of the action, but using it for adding behaviours can be problematic due to Interceptors that are defined at a much later stage. Because of that ActionSchedulers must NOT use this guid.
This action can only be executed if all of the inputs are not empty.
This action can only be executed if all of the inputs are not empty. An input can be explicitly marked as empty. If false, than one or more inputs can be empty to start execution.
Interceptors must not override this property, as certain behaviours of the data flow (Ex, execution pools) will be associated with this scheduling guid.
Interceptors must not override this property, as certain behaviours of the data flow (Ex, execution pools) will be associated with this scheduling guid. Also ActionScheduler will use this guid to track scheduled actions.
An action to be performed as part of a data flow. Actions declare what input labels they expect in order to start execution (0 .. N) and can produce outputs associated with the output labels (0 .. N). Executors will use these labels to execute to schedule the actions sequentially or in parallel.