Skip to main content
A decisions node manages and executes a decision table composed of a set of rules. The system evaluates each rule in order from top to bottom and returns the result of the first successful rule as the final result.

Rule

Each rule includes two parts:
  • conditions: A set of conditions to evaluate.
  • actions: The results to return when all conditions are satisfied.

Condition

Each condition includes a variable reference and a value expression. To simplify condition building and ensure correct syntax, use the DecisionsCondition class.
Variable Naming Convention: Conditions can reference all upstream variables using fully qualified path formats:
  • Agentic workflow inputs: flow.input.<variable_name>. For example, to check the grade input variable, use flow.input.grade.
  • Agentic workflow private variables: flow.private.<variable_name>
  • Upstream node outputs: use the variable path emitted by the upstream node
The following example checks whether the value of revenue_quote_ratio falls within the range from 0 (inclusive) to 50 (exclusive).
Python

Action

An action defines the result when all conditions in a rule are satisfied. Actions can reference agentic workflow output variables using the fully qualified path format flow.output.<variable_name>, or any other agentic workflow variable, such as flow.private.<variable_name>. You can also define a default action to return when no rules match.

Decision Table Columns

Decision table columns define the mapping between technical variable names and user-friendly display names in the agentic workflow Builder UI. Use the DecisionTableColumn class to specify columns for both conditions and actions.
Python

Locale

You can specify a locale string, such as en-US, fr-FR, or es-MX, to control how dates are parsed. Currently, locale only affects date parsing.

Example

In this example get_insurance_rate, you define a set of rules to calculate the insurance rate based on credit grade and loan amount:
Python
Note:
  • The decision_table_columns parameter is required for proper UI integration in agentic workflow Builder.