About Decision Tables
Decision tables contain logic used to determine how a rule behaves. A rule may use a single decision table or multiple decision tables that work in concert. Decision tables can contain rule actions.
A decision table that contains a manual decision point (task action) needs to be configured in a particular way:
The decision table must be process-aware. When creating the decision table, select the
Process Aware check box.
TaskData must be mapped.
The task’s Inputs/Outputs must match the decision table’s Inputs/Outputs.
Note: The decision table contains an extra parameter called ProcessData that is automatically generated when the decision table is created. This is mapped separately to the process, not to the task.
The decision table’s ProcessData must be mapped to the process.
Important: Do not overwrite or drop ProcessData as it contains necessary runtime data. ProcessData mappings must be only outgoing.
For more information about working with rule actions and decision tables, see webMethods BPM Rules Development Help.