Decision Tables Package

Design business rules within decision tables that affect Process routing. Decision tables can be reused in any Process model.


A Decision Table is a two-dimensional grid that outlines the different possible business conditions that can occur for a particular data output. 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.

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.

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

  • 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.

The Decision Tables package provides the following functions:

  • Design Decision Tables: Design Decision Tables in Decision Table Editor that can be reused in any Process to create complex yet easily configurable business rules. See these topics:

  • Decision Task connector: 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 variables in the Request to and from variables in the Decision Table(s). See Decision Task connector for more information.

Last updated