Description:

The EvalDecisionTable workflow step evaluates a selected decision table as part of a process. The step allows workflow Variables/Globals to be mapped to the decision table's input and output values.

The step supports:

• Selecting a Decision Table.
• Mapping Variables/Globals to decision table inputs and outputs.
• Returning all valid matches when configured.
• Restricting evaluation to provided input columns.
• Continuing the workflow through Matched or NoMatch paths.
• Using decision-table results in subsequent workflow activities.

Usage:

The EvalDecisionTable step is typically placed after the workflow has collected the information required to evaluate a business rule.

A typical workflow pattern is:

Get/Collect Input → Decision Table → Process Result

For example:

Get Customer Information → Decision Table → Continue Processing

The workflow first obtains the required values, maps those values to the decision table inputs, evaluates the selected Decision Table, and then continues through the appropriate return path.

To use this step, we must configure the decision table using the FlowWright decision configuration. To do this, navigate to the Manage Config > Decision Tables page. Then click Actions > Create. Provide a name for the decision table. 

Use the Add sign (+) to add Input and Output columns. Provide meaningful names for the columns. Use the Add sign (+) to insert empty rows into the decision table. Enter the input and output values as shown below. Click the Save button. You may add multiple input and output values using the Add sign.  

A sample decision table is provided below. 

Typical Workflow Suggestions:

Evaluate Business Rules

Use the step when business rules have been defined in a Decision Table, and the workflow needs to evaluate those rules.

Example:

Get Request Data → Decision Table → Process Request

Workflow information can be mapped to the decision table inputs, and the resulting decision-table values can be mapped back to workflow Variables/Globals.

Determine Processing Path

Use the Matched and NoMatch return paths to determine what the workflow should do after decision-table evaluation.

Example:

Start → Decision Table

Matched → Continue Processing

**NoMatch → Manual Review`

This provides a clear workflow structure for handling both matching and non-matching scenarios.

Evaluate Customer or Request Rules

Use a decision table after you collect customer or request information.

Example:

Get Customer Data → Decision Table → Customer Processing

The relevant Variables/Globals can be mapped to the decision table inputs before the table is evaluated.

Evaluate Approval Rules

Use the step as part of an approval workflow where the decision table determines whether the supplied information matches configured rules.

Example:

Submit Request → Decision Table → Approval Processing

A Matched path can continue to the next stage of processing, while a NoMatch path can connect to an alternate process.

Evaluate Classification Rules

Use the step when a workflow needs to evaluate input values against a collection of predefined decision rules.

Example:

Collect Data → Decision Table → Classification Processing

The result of the decision-table evaluation can then be used by downstream activities.

Return Multiple Valid Matches

Enable Return All Valid Matches when the workflow needs to obtain all valid matching results rather than limiting processing to a single valid match.

Example:

Collect Input → Decision Table → Process Matching Results

The option is explicitly exposed by the step as an optional configuration property.

Use Only Supplied Inputs

Enable Use only provided input columns when the decision-table evaluation should use only the input columns provided through the workflow's configured mappings.

Example:

Prepare Required Inputs → Decision Table → Process Result

This option should be configured with awareness of the inputs required by the selected Decision Table.

Store Decision-Table Outputs in Workflow Variables

Use the mapping configuration to associate decision-table outputs with workflow Variables or Globals.

Example:

Get Input → Decision Table → Use Output

The decision table mapping configuration is specifically intended to map Variables/Globals to decision-table inputs and outputs.

Reuse Decision Results

After the decision table evaluates, downstream workflow activities can use the mapped output values.

Example:

Decision Table → Populate Form → Send Notification

The decision table can therefore serve as a rules-evaluation stage between input collection and subsequent workflow processing.

Handle No-Match Scenarios

A workflow should provide an appropriate path when no decision-table rule matches the supplied inputs.

Example:

Decision Table

→ Matched: Continue Process

→ NoMatch: Send for Review

The NoMatch return value is explicitly defined by the step and can be connected to an alternative workflow path.

Build Rule-Based Workflow Routing

Use the decision table as a centralized rule-evaluation point within a larger workflow.

Example:

Request Received → Prepare Inputs → Decision Table → Route Request

This separates workflow data preparation from decision-table evaluation and the processing that follows the result.

Evaluate Multiple Possible Outcomes

When a decision table can produce multiple valid matches, enable Return All valid matches and configure the mappings required to consume those results.

Example:

Collect Request Information → Decision Table → Process Matching Rules

This pattern can be useful where more than one configured rule may apply to the same set of supplied inputs.

Example:

Let’s build and execute the “evalDecisionTableDef” example.                        

• Create a new process definition named “evalDecisionTableDef” and open it in designer mode. 
• Drag an “evalDecisionTable” step to the canvas.
• Connect the dots between the “Start” step and “evalDecisionTable” steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, Matched, NoMatch, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Define a variable or a global to store input and output values.
• Click the "evalDecisionTable" step to configure its "Required" properties. Provide a name for the step. Select a decision table from the drop-down list. Click the button to map the variable or global to inputs and outputs. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to map the variable or global references to inputs and outputs. A pop-up window appears for configuration. Enter the variable or global values. Click the Save button. 

• Click the "evalDecisionTable" step to configure its "Optional" properties. Select “On” to return all valid matches for the search. Select “On” to use only the provided input columns. Click the Save button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Configure the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. 

• Render the process instance and click the Decision table step to view its properties. When the workflow reaches the step:
  • FlowWright uses the selected Decision Table.
  • The configured Variable/Global mappings provide the decision-table inputs and receive configured outputs.
  • The decision table is evaluated.
  • The workflow continues through the Matched or NoMatch return path.
  • Any configured output values can then be consumed by subsequent workflow activities.

After Execution:

• Select the process instance and render it to view.

• Click the “Decision Table” step to open the properties page.

• Check the execution information. If “step Return value” is “Matched,” click Matched to redirect the render decision table. The Matched Row is highlighted as shown below. 

Tips:

• Select the correct Decision Table before configuring the mappings.
• Give Variables and Globals meaningful names.
• Verify that all required decision-table inputs have appropriate workflow values.
• Review the Variable/Global mapping before executing the workflow.
• Test the workflow with representative input values.
• Test scenarios that produce a Matched result.
• Test scenarios that produce a NoMatch result.
• Verify that decision-table outputs are stored in the intended Variables/Globals.
• Use the Matched path for the workflow processing that should occur when a rule matches.
• Connect the NoMatch path to an appropriate alternate or exception-handling process.
• Use Return All valid matches when the workflow requires all valid matching results.
• Carefully configure Use only provided input columns when only a subset of the decision table's inputs should participate in evaluation.
• Verify the behavior of the selected Decision Table before using the step in production.
• Test boundary values and combinations of inputs represented by the decision table.
• Keep the Variable/Global mapping understandable and maintainable.
• When a Decision Table is changed, retest workflows that use the table.
• Verify downstream activities after changing decision-table outputs or mappings.
• Document important decision-table mappings so that workflow maintainers understand where inputs and outputs originate.
• If a workflow depends on multiple matching results, test the workflow with data that produces more than one valid match.
• Do not assume decision-table matching behavior beyond what is documented for the selected Decision Table implementation.

Definition Sample:

You may provide a sample FlowWright Process Definition demonstrating the EvalDecisionTable step.

When importing the sample definition, verify and complete any missing configuration, including:

• Selected Decision Table.
• Variable/Global input mappings.
• Variable/Global output mappings.
• Return All valid matches setting.
• Use only provided input columns setting.
• Workflow Variable references.
• Environment-specific configuration.
• Matched workflow path.
• NoMatch workflow path.
• Downstream activities that consume decision-table outputs.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.