Decision Model and Notation is a graphical language used to specify business decisions. DMN helps convert complex decision-making code into easily readable diagrams.
To create and link a DMN action to a task node in FLOWX, follow these steps:
For a visual guide, refer to the following recording:
Consider a scenario where a bank needs to perform client information tasks/actions to send salutations, similar to what was previously created using MVEL here.
A business person or specialist can use DMN to design this business rule, without having to delve into technical definitions.
Here is an example of an MVEL script defined as a business rule action inside a Service Task node:
The previous example can be easily transformed into a DMN Business Rule action represented by the decision table:
In the example above, we used FEEL expression language to write the rules that should be met for the output to occur. FEEL defines a syntax for expressing conditions that input data should be evaluated against.
Input - In the example above, we used the user-selected gender from the first screen as input, bound to the application.client.gender
key.
Output - In the example above, we used the salutation (bound to application.client.salutation
) computed based on the user’s gender selection.
DMN also defines an XML schema that allows DMN models to be used across multiple DMN authoring platforms. The following output is the XML source of the decision table example from the previous section:
Decision Model and Notation is a graphical language used to specify business decisions. DMN helps convert complex decision-making code into easily readable diagrams.
To create and link a DMN action to a task node in FLOWX, follow these steps:
For a visual guide, refer to the following recording:
Consider a scenario where a bank needs to perform client information tasks/actions to send salutations, similar to what was previously created using MVEL here.
A business person or specialist can use DMN to design this business rule, without having to delve into technical definitions.
Here is an example of an MVEL script defined as a business rule action inside a Service Task node:
The previous example can be easily transformed into a DMN Business Rule action represented by the decision table:
In the example above, we used FEEL expression language to write the rules that should be met for the output to occur. FEEL defines a syntax for expressing conditions that input data should be evaluated against.
Input - In the example above, we used the user-selected gender from the first screen as input, bound to the application.client.gender
key.
Output - In the example above, we used the salutation (bound to application.client.salutation
) computed based on the user’s gender selection.
DMN also defines an XML schema that allows DMN models to be used across multiple DMN authoring platforms. The following output is the XML source of the decision table example from the previous section: