Chapter 6. Creating and editing DMN models in Business Central You can use the DMN designer in Business Central to design DMN decision requirements diagrams (DRDs) and define decision logic for a complete and functional DMN decision model. Red Hat Process Automation Manager provides design support for DMN 1.2 models at conformance level 3, and includes enhancements and fixes to FEEL and DMN model components to optimize the experience of implementing DMN decision services with Red Hat Process Automation Manager. Red Hat Process Automation Manager also provides runtime support for DMN 1.1, 1.2, 1.3, and 1.4 models at conformance level 3, but any DMN 1.1 and 1.3 models (do not contain DMN 1.3 features) that you import into Business Central, open in the DMN designer, and save are converted to DMN 1.2 models. Procedure In Business Central, go to Menu Design Projects and click the project name. Create or import a DMN file in your Business Central project. To create a DMN file, click Add Asset DMN , enter an informative DMN model name, select the appropriate Package , and click Ok . To import an existing DMN file, click Import Asset , enter the DMN model name, select the appropriate Package , select the DMN file to upload, and click Ok . The new DMN file is now listed in the DMN panel of the Project Explorer , and the DMN decision requirements diagram (DRD) canvas appears. Note If you imported a DMN file that does not contain layout information, the imported decision requirements diagram (DRD) is formatted automatically in the DMN designer. Click Save in the DMN designer to save the DRD layout. If an imported DRD is not automatically formatted, you can select the Perform automatic layout icon in the upper-right toolbar in the DMN designer to format the DRD. Begin adding components to your new or imported DMN decision requirements diagram (DRD) by clicking and dragging one of the DMN nodes from the left toolbar: Figure 6.1. Adding DRD components The following DRD components are available: Decision : Use this node for a DMN decision, where one or more input elements determine an output based on defined decision logic. Business knowledge model : Use this node for reusable functions with one or more decision elements. Decisions that have the same logic but depend on different sub-input data or sub-decisions use business knowledge models to determine which procedure to follow. Knowledge source : Use this node for external authorities, documents, committees, or policies that regulate a decision or business knowledge model. Knowledge sources are references to real-world factors rather than executable business rules. Input data : Use this node for information used in a decision node or a business knowledge model. Input data usually includes business-level concepts or objects relevant to the business, such as loan applicant data used in a lending strategy. Text annotation : Use this node for explanatory notes associated with an input data node, decision node, business knowledge model, or knowledge source. Decision service : Use this node to enclose a set of reusable decisions implemented as a decision service for invocation. A decision service can be used in other DMN models and can be invoked from an external application or a BPMN business process. In the DMN designer canvas, double-click the new DRD node to enter an informative node name. If the node is a decision or business knowledge model, select the node to display the node options and click the Edit icon to open the DMN boxed expression designer to define the decision logic for the node: Figure 6.2. Opening a new decision node boxed expression Figure 6.3. Opening a new business knowledge model boxed expression By default, all business knowledge models are defined as boxed function expressions containing a literal FEEL expression, a nested context expression of an external JAVA or PMML function, or a nested boxed expression of any type. For decision nodes, you click the undefined table to select the type of boxed expression you want to use, such as a boxed literal expression, boxed context expression, decision table, or other DMN boxed expression. Figure 6.4. Selecting the logic type for a decision node For business knowledge models, you click the top-left function cell to select the function type, or right-click the function value cell, select Clear , and select a boxed expression of another type. Figure 6.5. Selecting the function or other logic type for a business knowledge model In the selected boxed expression designer for either a decision node (any expression type) or business knowledge model (function expression), click the applicable table cells to define the table name, variable data types, variable names and values, function parameters and bindings, or FEEL expressions to include in the decision logic. You can right-click cells for additional actions where applicable, such as inserting or removing table rows and columns or clearing table contents. The following is an example decision table for a decision node that determines credit score ratings based on a defined range of a loan applicant's credit score: Figure 6.6. Decision node decision table for credit score rating The following is an example boxed function expression for a business knowledge model that calculates mortgage payments based on principal, interest, taxes, and insurance (PITI) as a literal expression: Figure 6.7. Business knowledge model function for PITI calculation After you define the decision logic for the selected node, click Back to "<MODEL_NAME>" to return to the DRD view. For the selected DRD node, use the available connection options to create and connect to the node in the DRD, or click and drag a new node onto the DRD canvas from the left toolbar. The node type determines which connection options are supported. For example, an Input data node can connect to a decision node, knowledge source, or text annotation using the applicable connection type, whereas a Knowledge source node can connect to any DRD element. A Decision node can connect only to another decision or a text annotation. The following connection types are available, depending on the node type: Information requirement : Use this connection from an input data node or decision node to another decision node that requires the information. Knowledge requirement : Use this connection from a business knowledge model to a decision node or to another business knowledge model that invokes the decision logic. Authority requirement : Use this connection from an input data node or a decision node to a dependent knowledge source or from a knowledge source to a decision node, business knowledge model, or another knowledge source. Association : Use this connection from an input data node, decision node, business knowledge model, or knowledge source to a text annotation. Figure 6.8. Connecting credit score input to the credit score rating decision Continue adding and defining the remaining DRD components of your decision model. Periodically click Save in the DMN designer to save your work. Note As you periodically save a DRD, the DMN designer performs a static validation of the DMN model and might produce error messages until the model is defined completely. After you finish defining the DMN model completely, if any errors remain, troubleshoot the specified problems accordingly. After you add and define all components of the DRD, click Save to save and validate the completed DRD. To adjust the DRD layout, you can select the Perform automatic layout icon in the upper-right toolbar of the DMN designer. The following is an example DRD for a loan prequalification decision model: Figure 6.9. Completed DRD for loan prequalification The following is an example DRD for a phone call handling decision model using a reusable decision service: Figure 6.10. Completed DRD for phone call handling with a decision service In a DMN decision service node, the decision nodes in the bottom segment incorporate input data from outside of the decision service to arrive at a final decision in the top segment of the decision service node. The resulting top-level decisions from the decision service are then implemented in any subsequent decisions or business knowledge requirements of the DMN model. You can reuse DMN decision services in other DMN models to apply the same decision logic with different input data and different outgoing connections. 6.1. Defining DMN decision logic in boxed expressions in Business Central Boxed expressions in DMN are tables that you use to define the underlying logic of decision nodes and business knowledge models in a decision requirements diagram (DRD). Some boxed expressions can contain other boxed expressions, but the top-level boxed expression corresponds to the decision logic of a single DRD artifact. While DRDs represent the flow of a DMN decision model, boxed expressions define the actual decision logic of individual nodes. DRDs and boxed expressions together form a complete and functional DMN decision model. You can use the DMN designer in Business Central to define decision logic for your DRD components using built-in boxed expressions. Prerequisites A DMN file is created or imported in Business Central. Procedure In Business Central, go to Menu Design Projects , click the project name, and select the DMN file you want to modify. In the DMN designer canvas, select a decision node or business knowledge model node that you want to define and click the Edit icon to open the DMN boxed expression designer: Figure 6.11. Opening a new decision node boxed expression Figure 6.12. Opening a new business knowledge model boxed expression By default, all business knowledge models are defined as boxed function expressions containing a literal FEEL expression, a nested context expression of an external JAVA or PMML function, or a nested boxed expression of any type. For decision nodes, you click the undefined table to select the type of boxed expression you want to use, such as a boxed literal expression, boxed context expression, decision table, or other DMN boxed expression. Figure 6.13. Selecting the logic type for a decision node For business knowledge model nodes, you click the top-left function cell to select the function type, or right-click the function value cell, select Clear , and select a boxed expression of another type. Figure 6.14. Selecting the function or other logic type for a business knowledge model For this example, use a decision node and select Decision Table as the boxed expression type. A decision table in DMN is a visual representation of one or more rules in a tabular format. Each rule consists of a single row in the table, and includes columns that define the conditions (input) and outcome (output) for that particular row. Click the input column header to define the name and data type for the input condition. For example, name the input column Credit Score.FICO with a number data type. This column specifies numeric credit score values or ranges of loan applicants. Click the output column header to define the name and data type for the output values. For example, name the output column Credit Score Rating and to the Data Type option, click Manage to go to the Data Types page where you can create a custom data type with score ratings as constraints. Figure 6.15. Managing data types for a column header value On the Data Types page, click New Data Type to add a new data type or click Import Data Object to import an existing data object from your project that you want to use as a DMN data type. If you import a data object from your project as a DMN data type and then that object is updated, you must re-import the data object as a DMN data type to apply the changes in your DMN model. For this example, click New Data Type and create a Credit_Score_Rating data type as a string : Figure 6.16. Adding a new data type Click Add Constraints , select Enumeration from the drop-down options, and add the following constraints: "Excellent" "Good" "Fair" "Poor" "Bad" Figure 6.17. Adding constraints to the new data type To change the order of data type constraints, you can click the left end of the constraint row and drag the row as needed: Figure 6.18. Dragging constraints to change constraint order For information about constraint types and syntax requirements for the specified data type, see the Decision Model and Notation specification . Click OK to save the constraints and click the check mark to the right of the data type to save the data type. Return to the Credit Score Rating decision table, click the Credit Score Rating column header, and set the data type to this new custom data type. Use the Credit Score.FICO input column to define credit score values or ranges of values, and use the Credit Score Rating column to specify one of the corresponding ratings you defined in the Credit_Score_Rating data type. Right-click any value cell to insert or delete rows (rules) or columns (clauses). Figure 6.19. Decision node decision table for credit score rating After you define all rules, click the top-left corner of the decision table to define the rule Hit Policy and Builtin Aggregator (for COLLECT hit policy only). The hit policy determines how to reach an outcome when multiple rules in a decision table match the provided input values. The built-in aggregator determines how to aggregate rule values when you use the COLLECT hit policy. Figure 6.20. Defining the decision table hit policy The following example is a more complex decision table that determines applicant qualification for a loan as the concluding decision node in the same loan prequalification decision model: Figure 6.21. Decision table for loan prequalification For boxed expression types other than decision tables, you follow these guidelines similarly to navigate the boxed expression tables and define variables and parameters for decision logic, but according to the requirements of the boxed expression type. Some boxed expressions, such as boxed literal expressions, can be single-column tables, while other boxed expressions, such as function, context, and invocation expressions, can be multi-column tables with nested boxed expressions of other types. For example, the following boxed context expression defines the parameters that determine whether a loan applicant can meet minimum mortgage payments based on principal, interest, taxes, and insurance (PITI), represented as a front-end ratio calculation with a sub-context expression: Figure 6.22. Boxed context expression for front-end client PITI ratio The following boxed function expression determines a monthly mortgage installment as a business knowledge model in a lending decision, with the function value defined as a nested context expression: Figure 6.23. Boxed function expression for installment calculation in business knowledge model For more information and examples of each boxed expression type, see Section 4.4, "DMN decision logic in boxed expressions" . 6.2. Creating custom data types for DMN boxed expressions in Business Central In DMN boxed expressions in Business Central, data types determine the structure of the data that you use within an associated table, column, or field in the boxed expression. You can use default DMN data types (such as String, Number, Boolean) or you can create custom data types to specify additional fields and constraints that you want to implement for the boxed expression values. Custom data types that you create for a boxed expression can be simple or structured: Simple data types have only a name and a type assignment. Example: Age (number) . Structured data types contain multiple fields associated with a parent data type. Example: A single type Person containing the fields Name (string) , Age (number) , Email (string) . Prerequisites A DMN file is created or imported in Business Central. Procedure In Business Central, go to Menu Design Projects , click the project name, and select the DMN file you want to modify. In the DMN designer canvas, select a decision node or business knowledge model for which you want to define the data types and click the Edit icon to open the DMN boxed expression designer. If the boxed expression is for a decision node that is not yet defined, click the undefined table to select the type of boxed expression you want to use, such as a boxed literal expression, boxed context expression, decision table, or other DMN boxed expression. Figure 6.24. Selecting the logic type for a decision node Click the cell for the table header, column header, or parameter field (depending on the boxed expression type) for which you want to define the data type and click Manage to go to the Data Types page where you can create a custom data type. Figure 6.25. Managing data types for a column header value You can also set and manage custom data types for a specified decision node or business knowledge model node by selecting the Properties icon in the upper-right corner of the DMN designer: Figure 6.26. Managing data types in decision requirements diagram (DRD) properties The data type that you define for a specified cell in a boxed expression determines the structure of the data that you use within that associated table, column, or field in the boxed expression. In this example, an output column Credit Score Rating for a DMN decision table defines a set of custom credit score ratings based on an applicant's credit score. On the Data Types page, click New Data Type to add a new data type or click Import Data Object to import an existing data object from your project that you want to use as a DMN data type. If you import a data object from your project as a DMN data type and then that object is updated, you must re-import the data object as a DMN data type to apply the changes in your DMN model. For this example, click New Data Type and create a Credit_Score_Rating data type as a string : Figure 6.27. Adding a new data type If the data type requires a list of items, enable the List setting. Click Add Constraints , select Enumeration from the drop-down options, and add the following constraints: "Excellent" "Good" "Fair" "Poor" "Bad" Figure 6.28. Adding constraints to the new data type To change the order of data type constraints, you can click the left end of the constraint row and drag the row as needed: Figure 6.29. Dragging constraints to change constraint order For information about constraint types and syntax requirements for the specified data type, see the Decision Model and Notation specification . Click OK to save the constraints and click the check mark to the right of the data type to save the data type. Return to the Credit Score Rating decision table, click the Credit Score Rating column header, set the data type to this new custom data type, and define the rule values for that column with the rating constraints that you specified. Figure 6.30. Decision table for credit score rating In the DMN decision model for this scenario, the Credit Score Rating decision flows into the following Loan Prequalification decision that also requires custom data types: Figure 6.31. Decision table for loan prequalification Continuing with this example, return to the Data Types window, click New Data Type , and create a Loan_Qualification data type as a Structure with no constraints. When you save the new structured data type, the first sub-field appears so that you can begin defining nested data fields in this parent data type. You can use these sub-fields in association with the parent structured data type in boxed expressions, such as nested column headers in decision tables or nested table parameters in context or function expressions. For additional sub-fields, select the addition icon to the Loan_Qualification data type: Figure 6.32. Adding a new structured data type with nested fields For this example, under the structured Loan_Qualification data type, add a Qualification field with "Qualified" and "Not Qualified" enumeration constraints, and a Reason field with no constraints. Add also a simple Back_End_Ratio and a Front_End_Ratio data type, both with "Sufficient" and "Insufficient" enumeration constraints. Click the check mark to the right of each data type that you create to save your changes. Figure 6.33. Adding nested data types with constraints To change the order or nesting of data types, you can click the left end of the data type row and drag the row as needed: Figure 6.34. Dragging data types to change data type order or nesting Return to the decision table and, for each column, click the column header cell, set the data type to the new corresponding custom data type, and define the rule values as needed for the column with the constraints that you specified, if applicable. Figure 6.35. Decision table for loan prequalification For boxed expression types other than decision tables, you follow these guidelines similarly to navigate the boxed expression tables and define custom data types as needed. For example, the following boxed function expression uses custom tCandidate and tProfile structured data types to associate data for online dating compatibility: Figure 6.36. Boxed function expression for online dating compatibility Figure 6.37. Custom data type definitions for online dating compatibility Figure 6.38. Parameter definitions with custom data types for online dating compatibility 6.3. Included models in DMN files in Business Central In the DMN designer in Business Central, you can use the Included Models tab to include other DMN models and Predictive Model Markup Language (PMML) models from your project in a specified DMN file. When you include a DMN model within another DMN file, you can use all of the nodes and logic from both models in the same decision requirements diagram (DRD). When you include a PMML model within a DMN file, you can invoke that PMML model as a boxed function expression for a DMN decision node or business knowledge model node. You cannot include DMN or PMML models from other projects in Business Central. 6.3.1. Including other DMN models within a DMN file in Business Central In Business Central, you can include other DMN models from your project in a specified DMN file. When you include a DMN model within another DMN file, you can use all of the nodes and logic from both models in the same decision requirements diagram (DRD), but you cannot edit the nodes from the included model. To edit nodes from included models, you must update the source file for the included model directly. If you update the source file for an included DMN model, open the DMN file where the DMN model is included (or close an re-open) to verify the changes. You cannot include DMN models from other projects in Business Central. Prerequisites The DMN models are created or imported (as .dmn files) in the same project in Business Central as the DMN file in which you want to include the models. Procedure In Business Central, go to Menu Design Projects , click the project name, and select the DMN file you want to modify. In the DMN designer, click the Included Models tab. Click Include Model , select a DMN model from your project in the Models list, enter a unique name for the included model, and click Include : Figure 6.39. Including a DMN model The DMN model is added to this DMN file, and all DRD nodes from the included model are listed under Decision Components in the Decision Navigator view: Figure 6.40. DMN file with decision components from the included DMN model All data types from the included model are also listed in read-only mode in the Data Types tab for the DMN file: Figure 6.41. DMN file with data types from the included DMN model In the Model tab of the DMN designer, click and drag the included DRD components onto the canvas to begin implementing them in your DRD: Figure 6.42. Adding DRD components from the included DMN model To edit DRD nodes or data types from included models, you must update the source file for the included model directly. If you update the source file for an included DMN model, open the DMN file where the DMN model is included (or close an re-open) to verify the changes. To edit the included model name or to remove the included model from the DMN file, use the Included Models tab in the DMN designer. Important When you remove an included model, any nodes from that included model that are currently used in the DRD are also removed. 6.3.2. Including PMML models within a DMN file in Business Central In Business Central, you can include Predictive Model Markup Language (PMML) models from your project in a specified DMN file. When you include a PMML model within a DMN file, you can invoke that PMML model as a boxed function expression for a DMN decision node or business knowledge model node. If you update the source file for an included PMML model, you must remove and re-include the PMML model in the DMN file to apply the source changes. You cannot include PMML models from other projects in Business Central. Prerequisites The PMML models are imported (as .pmml files) in the same project in Business Central as the DMN file in which you want to include the models. Procedure In your DMN project, add the following dependencies to the project pom.xml file to enable PMML evaluation: <!-- Required for the PMML compiler --> <dependency> <groupId>org.drools</groupId> <artifactId>kie-pmml</artifactId> <version>USD{rhpam.version}</version> <scope>provided</scope> </dependency> <!-- Alternative dependencies for JPMML Evaluator, override `kie-pmml` dependency --> <dependency> <groupId>org.kie</groupId> <artifactId>kie-dmn-jpmml</artifactId> <version>USD{rhpam.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.jpmml</groupId> <artifactId>pmml-evaluator</artifactId> <version>1.5.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.jpmml</groupId> <artifactId>pmml-evaluator-extension</artifactId> <version>1.5.1</version> <scope>provided</scope> </dependency> To access the project pom.xml file in Business Central, you can select any existing asset in the project and then in the Project Explorer menu on the left side of the screen, click the Customize View gear icon and select Repository View pom.xml . If you want to use the full PMML specification implementation with the Java Evaluator API for PMML (JPMML), use the alternative set of JPMML dependencies in your DMN project. If the JPMML dependencies and the standard kie-pmml dependency are both present, the kie-pmml dependency is disabled. For information about JPMML licensing terms, see Openscoring.io . Important The legacy kie-pmml dependency is deprecated with Red Hat Process Automation Manager 7.10.0 and will be replaced by kie-pmml-trusty dependency in a future Red Hat Process Automation Manager release. Note Instead of specifying a Red Hat Process Automation Manager <version> for individual dependencies, consider adding the Red Hat Business Automation bill of materials (BOM) dependency to dependencyManagement section of your project pom.xml file. The Red Hat Business Automation BOM applies to both Red Hat Decision Manager and Red Hat Process Automation Manager. When you add the BOM files, the correct versions of transitive dependencies from the provided Maven repositories are included in the project. Example BOM dependency: <dependency> <groupId>com.redhat.ba</groupId> <artifactId>ba-platform-bom</artifactId> <version>7.13.5.redhat-00002</version> <scope>import</scope> <type>pom</type> </dependency> For more information about the Red Hat Business Automation BOM, see What is the mapping between RHPAM product and maven library version? . If you added the JPMML dependencies in your DMN project to use the JPMML Evaluator, download the following JAR files and add them to the ~/kie-server.war/WEB-INF/lib and ~/business-central.war/WEB-INF/lib directories in your Red Hat Process Automation Manager distribution: kie-dmn-jpmml JAR file in the Red Hat Process Automation Manager 7.13.5 Maven Repository distribution ( rhpam-7.13.5-maven-repository/maven-repository/org/kie/kie-dmn-jpmml/7.67.0.Final-redhat-00024/kie-dmn-jpmml-7.67.0.Final-redhat-00024.jar ) from the Red Hat Customer Portal JPMML Evaluator 1.5.1 JAR file from the online Maven repository JPMML Evaluator Extensions 1.5.1 JAR file from the online Maven repository These artifacts are required to enable JPMML evaluation in KIE Server and Business Central. Important Red Hat supports integration with the Java Evaluator API for PMML (JPMML) for PMML execution in Red Hat Process Automation Manager. However, Red Hat does not support the JPMML libraries directly. If you include JPMML libraries in your Red Hat Process Automation Manager distribution, see the Openscoring.io licensing terms for JPMML. In Business Central, go to Menu Design Projects , click the project name, and select the DMN file you want to modify. In the DMN designer, click the Included Models tab. Click Include Model , select a PMML model from your project in the Models list, enter a unique name for the included model, and click Include : Figure 6.43. Including a PMML model The PMML model is added to this DMN file: Figure 6.44. DMN file with included PMML model In the Model tab of the DMN designer, select or create the decision node or business knowledge model node in which you want to invoke the PMML model and click the Edit icon to open the DMN boxed expression designer: Figure 6.45. Opening a new decision node boxed expression Figure 6.46. Opening a new business knowledge model boxed expression Set the expression type to Function (default for business knowledge model nodes), click the top-left function cell, and select PMML . In the document and model rows in the table, double-click the undefined cells to specify the included PMML document and the relevant PMML model within that document: Figure 6.47. Adding a PMML model in a DMN business knowledge model Figure 6.48. Example PMML definition in a DMN business knowledge model If you update the source file for an included PMML model, you must remove and re-include the PMML model in the DMN file to apply the source changes. To edit the included model name or to remove the included model from the DMN file, use the Included Models tab in the DMN designer. 6.4. Creating DMN models with multiple diagrams in Business Central For complex DMN models, you can use the DMN designer in Business Central to design multiple DMN decision requirements diagrams (DRDs) that represent parts of the overall decision requirements graph (DRG) for the DMN decision model. In simple cases, you can use a single DRD to represent all of the overall DRG for the decision model, but in complex cases, a single DRD can become large and difficult to follow. Therefore, to better organize DMN decision models with many decision requirements, you can divide the model into smaller nested DRDs that constitute the larger central DRD representation of the overall DRG. Prerequisites You understand how to design DRDs in Business Central. For information about creating DRDs, see Chapter 6, Creating and editing DMN models in Business Central . Procedure In Business Central, navigate to your DMN project and create or import a DMN file in the project. Open the new or imported DMN file to view the DRD in the DMN designer, and begin designing or modifying the DRD using the DMN nodes in the left toolbar. For any DMN nodes that you want to define in a separate nested DRD, select the node, click the DRD Actions icon, and select from the available options. Figure 6.49. DRD actions icon for subdividing a DRD The following options are available: Create : Use this option to create a nested DRD where you can separately define the DMN components and diagram for the selected node. Add to : If you already created a nested DRD, use this option to add the selected node to an existing DRD. Remove : If the node that you selected is already within a nested DRD, use this option to remove the node from that nested DRD. After you create a nested DRD within your DMN decision model, the new DRD opens in a separate DRD canvas and the available DRD and components are listed in the Decision Navigator left menu. You can use the Decision Navigator menu to rename or remove a nested DRD. Figure 6.50. Rename new nested DRD in the Decision Navigator menu In the separate canvas for the new nested DRD, design the flow and logic for all required components in this portion of the DMN model, as usual. Continue adding and defining any other nested DRDs for your decision model and save the completed DMN file. For example, the following DRD for a loan prequalification decision model contains all DMN components for the model without any nested DRDs. This example relies on the single DRD for all components and logic, resulting in a large and complex diagram. Figure 6.51. Single DRD for loan prequalification Alternatively, by following the steps in this procedure, you can divide this example DRD into multiple nested DRDs to better organize the decision requirements, as shown in the following example: Figure 6.52. Multiple nested DRDs for loan prequalification Figure 6.53. Overview of front end ratio DRD Figure 6.54. DRD for front end ratio Figure 6.55. Overview of credit score rating DRD Figure 6.56. DRD for credit score rating Figure 6.57. Overview of back end ratio DRD Figure 6.58. DRD for back end ratio 6.5. DMN model documentation in Business Central In the DMN designer in Business Central, you can use the Documentation tab to generate a report of your DMN model that you can print or download as an HTML file for offline use. The DMN model report contains all decision requirements diagrams (DRDs), data types, and boxed expressions in your DMN model. You can use this report to share your DMN model details or as part of your internal reporting workflow. Figure 6.59. Example DMN model report 6.6. DMN designer navigation and properties in Business Central The DMN designer in Business Central provides the following additional features to help you navigate through the components and properties of decision requirements diagrams (DRDs). DMN file and diagram views In the upper-left corner of the DMN designer, select the Project Explorer view to navigate between all DMN and other files or select the Decision Navigator view to navigate between the decision components, graphs, and boxed expressions of a selected DRD: Figure 6.60. Project Explorer view Figure 6.61. Decision Navigator view Note The DRD components from any DMN models included in the DMN file (in the Included Models tab) are also listed in the Decision Components panel for the DMN file. In the upper-right corner of the DMN designer, select the Explore diagram icon to view an elevated preview of the selected DRD and to navigate between the nodes of the selected DRD: Figure 6.62. Explore diagram view DRD properties and design In the upper-right corner of the DMN designer, select the Properties icon to modify the identifying information, data types, and appearance of a selected DRD, DRD node, or boxed expression cell: Figure 6.63. DRD node properties To view the properties of the entire DRD, click the DRD canvas background instead of a specific node. DRD search In the upper-right corner of the DMN designer, use the search bar to search for text that appears in your DRD. The search feature is especially helpful in complex DRDs with many nodes: Figure 6.64. DRD search DMN decision service details Select a decision service node in the DMN designer to view additional properties, including Input Data , Encapsulated Decisions , and Output Decisions in the Properties panel. Figure 6.65. Decision Service details

Commands:
<!-- Required for the PMML compiler --> <dependency> <groupId>org.drools</groupId> <artifactId>kie-pmml</artifactId> <version>USD{rhpam.version}</version> <scope>provided</scope> </dependency> <!-- Alternative dependencies for JPMML Evaluator, override `kie-pmml` dependency --> <dependency> <groupId>org.kie</groupId> <artifactId>kie-dmn-jpmml</artifactId> <version>USD{rhpam.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.jpmml</groupId> <artifactId>pmml-evaluator</artifactId> <version>1.5.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.jpmml</groupId> <artifactId>pmml-evaluator-extension</artifactId> <version>1.5.1</version> <scope>provided</scope> </dependency>
<dependency> <groupId>com.redhat.ba</groupId> <artifactId>ba-platform-bom</artifactId> <version>7.13.5.redhat-00002</version> <scope>import</scope> <type>pom</type> </dependency>