What is a Decision Table?

Understand what a Decision Table is in ProcessMaker Platform.

Overview

A Decision Table is a two-dimensional grid that outlines the different possible business rules that can occur, and then specifies the data output for each. The data output then affects the workflow routing for any Request that references that Decision Table. The Decision Table represents business rules from which to evaluate how to route Requests for a Process.

Decision Tables are Decision Model and Notation (DMN) files. DMN is a standard notation to model and run decisions in business contexts, used by business analysts, developers, and Process designers to manage complex decision-making scenarios.

Use Decision Task connectors to run Decision Tables in your Processes. Specify which Decision Table(s) to run, thereby evaluating their business rules, and then map how data routes between Request variables to and from Decision Table variables.

Decision Task connectors immediately evaluate the business rules within a specified Decision Table, thereby affecting Request workflow routing in real time with the current conditions and outcomes for all decisions in that Decision Table.

See Components of a Decision Table for more information.

Below is an example of a Decision Table for Loan Request Approval Rules as edited in Decision Table Editor.

An example Decision Table for Loan Request Approval rules as edited in Decision Table Editor

Why Use Decision Tables?

Decision Tables provide the following benefits versus only use BPMN elements to determine workflow routing:

• Design complex sets of business rules more easily and with greater readability and transparency than using Gateway-type elements with Sequence Flow elements to determine workflow routing.

• Decision Tables require no coding experience, allow most Process designers to easily design business rules.

• Test a Decision Table to evaluated expected outcomes from decisions within the table. There is no need to start Requests to evaluate decisions, which would trigger security log events and produce Saved Search results.

• Decision Tables function independently of Process models. Decision Tables are referenced from within Process models, thereby making them reusable and more flexible than only using BPMN elements.

• Reference Request variables and data within Collections by using mustache syntax. In doing so, create expressions that evaluate expressions containing dynamic values.

• Decision Tables are referenced from Rule Task connectors in a Process model. One Rule Task connector may reference multiple Decision Tables to determine complex routing decisions.

Related Topics

pageDecision Table Best PracticespageManage Decision Tables