Variables

Variables represent values used during rule execution. They provide a way to reference and reuse data inside rules instead of working with hardcoded values directly.

A variable can contain data provided to the rule, values created during execution, or results produced by the rule itself. Once available, the value can be reused in other conditions, calculations, expressions, or execution steps.

The available variable types and variable addressing syntax depend on the selected rule type.

---

Variables by Rule Type

In this section you can find list of variables available for each rule type.

Decision Tables

Decision Tables support:

• Input Model Variables

• Output Model Variables

• Rule Variables

• Column Variables

Column Variables

Columns inside a Decision Table can reference values from previously evaluated columns.

This applies to:

• Condition columns

• Calculation columns

• Result columns

In each Decison Table row scenario columns are evaluated from left to right, therefore a column can only reference columns that were already evaluated earlier in the table.

If a variable reference is used before the referenced value is created or evaluated, the variable will not be recognized.

Example of variables being used correctly in Decision Table:

• Columns are referensed after their declaration/evaluation.

Incorrect use of column references in Decision Tables:

• Column is referensed before its evaluation therefore its not recognized.

{basicPrice}  //variable from input model
{discount}    //created calculation column variable

---

Decision Trees

Decision Trees support:

• Input Model Variables

• Output Model Variables

• Rule Variables

{package.weight}  //variable from input model
{rate}            //created rule variable

Variables are commonly used in node conditions and result branches.

Example how to use variables in Decision tree:

---

Scripting Rules

Scripting Rules support:

• Input Model Variables

• Output Model Variables

• Rule variables

Variables are referenced using dot notation.

Example of variables used in Scripting Rule:

input.customer.country   //variable from IO model
ruleVariables.rate       //created rule variable
output.result            //variable from IO model

---

Decision Flows and Integration Flows

Decision Flows and Integration Flows support:

• Input Model Variables

• Output Model Variables

• Variables created in flow and during flow execution

Variables can be reused between nodes and flow steps.

Both curly bracket syntax and dot notation are supported here.

{input.age}             //variable from IO model
{rule.output.pricing}   //variable referencing output of evaluated business rule
{globalVariable.rate}   //created global variable
{newVariable}           //new variable created in flow
{output.result}         //variable from IO model

---

AI Agents

AI Agents support:

• Input Model Variables

• Output Model Variables

• Attachments

• Rule Variables

Attachments and generated values can be reused during execution.

{customer.age}             //variable from input model
{attachement.policies.pdf} //variable referencing attachement added to the ai rule

---

Lookup Tables

Lookup Tables do not support:

• Model Variables

• Rule Variables

They operate only with values defined directly inside the table.

---

Rule Variables

Rule Variables are variables created within the context of a specific rule.

They are typically used for:

• Temporary values

• Intermediate calculations

• Shared reusable values inside the rule

Rule Variables exist only during the current rule execution.

Detailed information about Rule Variables is available on the dedicated Rule Variables documentation page.