Reports are entities that collect, filter, organize and display data in different formats, such as a table, matrix, summary, or chart. Reportable data can be sourced from the system itself, flows, folders or integrated systems, and filtered according to the sources’ contents.
This tutorial demonstrates how to use Rule Extensions in Rule Engine. Rule Engine Extension is a Rule Behavior implemented in Decisions 3.2. This Rule Behavior allows to create a Rule that can be embedded...
This tutorial demonstrates how to use Multiple Outcomes from the Truth Table. This feature is implemented in Decisions 3.2. Data Return Rule (Multiple) option is a new Truth Table Type that can be set...
List Container Rules implemented in Decisions 3.2.0 in Rule Engine. These Rules are designed to process a list of items and apply desirable conditions to each item in the list. List Container...
Flow and Rule Sets are a common set of rules and flows that can be parameterized or customized based on context without the need to copy or rewrite them. The Rule Set allows you to define a number of...
Interceptor Rule is a step that behaves like an Assigned Form. With this step user can review or manually edit current Data in the Flow. Moreover, user can apply custom Rules to data or Automate data processing. Example: In...
This tutorial demonstrates how to use Rule Engine Extension / Evaluate Rule Flow behavior. This Flow Behavior type is used to expose Flow as a Verb for the Rule Engine. In other words, we can create...
Sequential Rule was introduced in Decisions 3.2 version. This type of Rule is basically a Flow that represents a sequence of steps that evaluate data. It can be used when the designer wants to embed...
Rules evaluate a data input and return an outcome that is dependent on whether the input satisfies the rule's conditions. Before using a rule in a production scenario, it can be useful to test it with the Rule Debugger.
Rules evaluate a data input and typically return an outcome of true or false, depending on whether the input satisfies the rule's conditions. Rules can also output data objects instead of a simple true or false value, depending on whether the rule is satisfied.
Rules evaluate a data input and return an outcome that is dependent on whether the input satisfies the rule's conditions. Action Rules define specific actions (or flows) that will be run in either case, as opposed to the more typical True or False outcomes that are outputted by logical rules.
The rule engine supplies nearly all the rule verbs you will need, however some cases require custom complex verbs. In this situation, the rule engine allows users to define their own verbs. These "custom...
The rule engine has a unit test framework that allows you to write a suite of tests and execute them against your rule. This allows you to quickly see if your rule is returning the expected results. This functionality is...
Truth tables are rules that compare the possible combinations of multiple inputs, allowing the user to arrive at different outcomes depending on the specific combination. Example In our example flow,...
Flow and rule sets are a common set of rules and flows that can be parameterized or customized based on context without the need to copy or rewrite them. The Flow Set allows you to define a number of rules...