A Decision is a grouping of business rules that determines output values based on a set of inputs. Unlike expression rules, which primarily calculate or manipulate data, Decisions are best used to encapsulate complex, business-specific logic. Decisions are configured in the decision designer, which enables fast, intuitive implementation of business logic without using expressions by way of decision tables.
Decisions can be called from any expression, so they can be reused across multiple objects throughout the system.
Each time you modify and save a Decision, a new version is created. All expressions that use the Decision use the latest version. All versions are accessible to designers who can view the Decision, and a Decision can be reverted back to a previous version at any time.
For step-by-step guidance on how to build your first Decision, see the Create a Decision page.
For examples of different Decision use cases, see the Appian Decisions page. These examples will help you understand how you can leverage Decisions in your applications.
Each Decision has the following properties:
|Name||The name that is used when evaluating the Decision. Names are case-insensitive and must be unique across Decisions, interfaces, expression rules, constants, and functions.|
|Description||Supplemental information about the Decision that is displayed in the inline help within the expression editor and the application contents grid.|
|Save In||The rule folder that the Decision is saved into.|
|Inputs||Inputs are used to pass data into the Decision.
|Decision Outputs||Decision outputs are the values that are returned when a Decision is evaluated.
|Decision Definition||The business logic that is defined as a decision table. The input values passed into the Decision are used to evaluate this logic to determine what rules in the table match. More information about how to specify this logic is below.|
|Hit Policy||Determines what a Decision returns when more than one business rule matches the inputs.|
The logic of a Decision is configured using a decision table. In a decision table, each column is either an input to the Decision or one of its outputs. Each row in the table respresents a decision rule, in which each cell is a logical operation. When all the cells' conditions for a particular row are true, the Decision will return the output values specified for that row.
The following types are available for Inputs:
A Decision is invalid if not all of its input values are defined. When a Decision with undefined values is evaluated, it will fail to return a value. The decision designer helps you identify if there are any missing or invalid values when you test and save your Decision.
The Decision output is used to specify what the Decision returns if a particular row's logic matches the passed in input values. Decision output columns are indicated by a gray background.
The following types are available for Decision outputs:
Decisions that are defined with Appian Objects as output values will have these objects identified as precedents to the Decision. Appian recommends only using objects that will exist in all of your environments for your Decisions.
Like inputs, a Decision can have multiple outputs. This is considered a compound output. When a Decision has a compound output, it will return a dictionary with fields that correspond to each output column of the Decision. The field names in the dictionary are the output names specified in the Decision.
Decisions have an explicit return type, this helps designers understand what to expect when integrating the Decision into their applications. The return type is displayed in the inline help within expression editors along side the Decision's description and inputs. A Decision's return type depends on the type of output, whether it has a compound output, and its hit policy.
|Hit Policy||Compound Output||Output Type|
|Unique, First||No||The type defined in the Decision's single output column. Available types are listed above.|
|Rule Order||No||The type defined in the Decision's single output column. Decisions with the Rule Order hit policy must output an array type.|
|Rule Order||Yes||List of Map|
When a Decision is evaluated but there are no matching rows and no default output is defined, the Decision will return either a null of its output type or an empty list of its output type if it is an array type (which is determined by the scenarios outlined in the table above).
In the Decision Model and Notation (DMN) standard, you can specify a default output for your decision. In the Appian decision designer, the last row in the decision table is used to define the decision's default output. The default output will be returned when the decision is evaluated but there are no matching rows.
Values for an input or output can be selected from a list instead of being specified free-form. The Use a dropdown to list values you can select for this input/output option in the input and output dialogs allows you to configure what values to choose from when defining that input or output. This configuration only constrains the experience of configuring the Decision, and has no effect on how the Decision evaluates.
This list of values can be defined in two ways:
The list of values can also have optional labels for choices in the list, similar to how dropdown components are defined. These choice labels are defined the same way the values are defined and will be what represents the value in the decision table. These labels are used to further improve the ease of configuring decision rules in the table, and have no effect on the Decision's execution or output values.
Decisions are defined in the decision designer by specifying logic in the decision table located in the main pane of the designer.
Each input cell in the decision table corresponds to a logical operation that is evaluated with the value passed into the input at exectuion time. When called, the Decision evaluates each row in order. If any cell in the row evaluates to false then the Decision stops evaluating that row. If all the logical conditions for a row evaluate to true, then that row is said to be a hit, or a match, and the Decision will result in the defined output value for that row. The Decision's hit policy determines whether it will continue to evaluate rows or finish once it has found a match.
The following logical operations are available per input type:
|Logical Operator||Description||Available Types|
|=||Equals. When using the list of values feature with Text and Integer types, multiple values can be selected and the operation will check if the Inputs equals any of the selected values.||All|
|not||Does not equal. When using the list of values feature with Text and Integer types, multiple values can be selected and the operation will check if the Inputs does not equal any of the selected values.||All|
|is null||The input value is null||All|
|not null||The input value is any value but null||All|
|any||The input can be any value, it is irrelevant in this row of logic. The cell will always evaluate to true.||All|
Note: For Date inputs, the operator's label is "before"
|Date, Number (Decimal), Number (Integer)|
Note: For Date inputs, the operator's label is "after"
|Date, Number (Decimal), Number (Integer)|
|<=||Less than or equal to||Number (Decimal), Number (Integer)|
|>=||Greater than or equal to||Number (Decimal), Number (Integer)|
|from||Inclusive range of values. Specify two numbers, and all values in that range, including those numbers, will be in the set. For example, "from 1 to 3" means the numbers 1, 2, and 3 are in the set.||Date, Number (Decimal), Number (Integer)|
|between||Exclusive range of values. Exclusive range of values. Specify two numbers, and all values strictly between those two numbers will be in the set. For example, "between 1 to 3" means only the number 2 is in the set. This is most useful for certain types of decimal value ranges.||Date, Number (Decimal), Number (Integer)|
The hit policy of a Decision specifies what the result of a Decision is in the cases of overlapping rules, i.e. when more than one row matches the input data. Hit policies are configured by clicking the "U" in the top left cell of the decision table in the decision designer. Appian supports a number of hit policies defined in the Decision Model and Notation (DMN) standard:
|Unique||Overlapping rules are not allowed. Only a single rule can ever be matched and all rows must be unique. Unique is the default hit policy for Decisions. The decision designer indicates which rows in your Decision overlap when using this hit policy. Decisions with the Unique hit policy will fail to evaluate if they contain overlapping logic. The Decision stops evaluating after finding the first match (in rule order).|
|First||Multiple (overlapping) rules can match. The first match by rule order is returned and the Decision stops evaluating.|
|Rule Order||Evaluates the entire Decision and returns outputs for all matches in row order. Decisions with the Rule Order hit policy must always return an array type.|
Testing your Decision in the decision designer gives you rapid feedback on what a given set of inputs will evaluate to, allowing you to quickly understand and adjust the decision to produce the exact results required. A Test button is displayed in the right pane. Clicking the button evaluates the Decision and displays the type and value of the result.
If you have one or more Inputs, you can enter values for each input in the Test Inputs section. These values are used when testing the Decision. You can save a default value for your test inputs by clicking the Set as default test values link in the designer. Once set, the default values will be saved with the decision. Default test values are always exported with the decision, but can only be imported if the destination environment has the Allow Test Values to Be Imported with Design Objects setting enabled. For more about this configuration, see the Deployment section of the Appian Administration Console page.
When testing your Decision, additional design information and validations are run and displayed on the decision table itself. See the Design Guidance and Validations section below.
In addition to allowing fast and intuitive configuration of your Decisions, the decision designer helps you create smarter Decisions with the following functionality:
When using the Unique hit policy, the designer will highlight which of your rows overlap with each other to identify when rules won't ever be matched. When a Unique hit policy Decision has overlapping rules, it will fail to evaluate. Overlapping rules are highlighted red on the decision table and when you hover over the error icon for that row, a tooltip will appear identifying which rows it overlaps with.
Additionally, when testing, the designer checks for completeness of your decision logic and identifies gaps in your logic. The completeness check icon will appear on the left side of an input's column header when there are gaps in the logic you defined for that input. Hovering over the icon will display a tooltip that identifies values that that input does not have logic accounting for. This design information is meant as a suggestion for helping you craft more robust Decisions and does not affect the evaluation of a Decision.
Completeness check identifies the following gaps:
The completeness check icon disappears once the identified missing gaps are covered.
Decisions are called using the
rule! domain. When calling a Decision, values or variables must be passed to the Inputs by keyword, as shown below.
rule!IQ_determineCarInsuranceQuote(age: pv!age, state: pv!state)
Each time you modify and save a decision, a new version is created. All objects that use the decision will use the latest version. All versions are accessible to designers who can view the decision, and a decision can be reverted back to a previous version at any time.
For information on how to manage object versions, see Managing Object Versions.
Users with Administrator permission to this object or rule folder can move it to another folder:
NOTE: Any objects that are configured to inherit the security of the parent folder assume the security rights of the target folder.
Deleting an Decision prevents users from further viewing or editing it. However, the last version of the Decision is still available to be used in processes, record views, and reports.
Decisions can be deleted by users with Administrator rights to it. Appian does not recommend deleting Decisions that are in use because the decision can no longer be exported.
To delete a Decision:
System Administrators have the ability to delete Decisions (and other objects) in bulk by selecting them and clicking Delete in the toolbar.
Renaming a decision will automatically update references to it in all objects. To rename a decision:
Learn more on Renaming Design Objects.
Any user can invoke any decision that is used by an interface or process they can access.
The security role map of a decision controls which developers can see or modify it and its properties. By default, decisions inherit the security of the folder that they are saved in. See Editing Object Security to modify a decision's security.
The following table outlines the actions that can be completed for each permission level in a decision's security role map:
|Evaluate the decision||Yes||Yes||Yes||Yes|
|View the decision definition||Yes||Yes||Yes||No|
|Duplicate the decision||Yes||Yes||Yes||No|
|Test the decision||Yes||Yes||Yes||No|
|Add, reorder, or delete rows in the decision||Yes||Yes||No||No|
|Update values for existing inputs and outputs||Yes||Yes||No||No|
|View the security||Yes||Yes||No||No|
|Rename the decision||Yes||Yes||No||No|
|Add, edit, or delete inputs and outputs||Yes||No||No||No|
|Edit the decision's hit policy||Yes||No||No||No|
|Delete the decision||Yes||No||No||No|
|Update the security||Yes||No||No||No|
Developers with Viewer permissions to this object can duplicate it. There are two ways to duplicate an object with a designer:
Once you select the Duplicate option, you will see the following dialog:
NOTE: You can only duplicate the most recent version of an object. If you have unsaved changes and attempt to duplicate the object from within the designer, the most recent saved version of the object will be duplicated without the unsaved changes. A banner appears when there are unsaved changes to remind you before duplicating.
Duplication from within an object is available for interfaces, expression rules, integrations, and decisions. Constants, in addition to the previously mentioned object types, can be duplicated from the toolbar button from anywhere within an application's context.
On This Page