BXMSDOC-6416-master: Add multi-DRD content to PAM/DM (#2861)

* BXMSDOC-6416-master: Add multi-DRD content for DMN.

* Peer review.

Author: sterobin

_images/dmn/dmn-bkm-edit.png

@@ -5,7 +5,7 @@ ifdef::context[:parent-context: {context}]
 :context: dmn-models
 
 // Purpose statement for the assembly
-As a business analyst or business rules developer, you can use Decision Model and Notation (DMN) to model a decision service graphically in a decision requirements diagram (DRD). This diagram consists of one or more decision requirements graphs (DRGs) that trace business decisions from start to finish, with each decision node using logic defined in DMN boxed expressions such as decision tables.
+As a business analyst or business rules developer, you can use Decision Model and Notation (DMN) to model a decision service graphically. The decision requirements of a DMN decision model are determined by a decision requirements graph (DRG) that is depicted in one or more decision requirements diagrams (DRDs). A DRD can represent part or all of the overall DRG for the DMN model. DRDs trace business decisions from start to finish, with each decision node using logic defined in DMN boxed expressions such as decision tables.
 
 {PRODUCT} provides design and runtime support for DMN 1.2 models at conformance level 3, and runtime-only support for DMN 1.1 and 1.3 models at conformance level 3. You can design your DMN models directly in {CENTRAL} or import existing DMN models into your {PRODUCT} projects for deployment and execution. DMN 1.1 and 1.3 models are currently not supported in the DMN designer in {CENTRAL}.
 
@@ -73,6 +73,8 @@ include::{drools-dir}/DMN/dmn-included-models-dmn-proc.adoc[leveloffset=+3]
 
 include::{drools-dir}/DMN/dmn-included-models-pmml-proc.adoc[leveloffset=+3]
 
+include::{drools-dir}/DMN/dmn-model-creating-multiples-proc.adoc[leveloffset=+2]
+
 include::{drools-dir}/DMN/dmn-documentation-con.adoc[leveloffset=+2]
 
 include::{drools-dir}/DMN/dmn-designer-nav-ref.adoc[leveloffset=+2]

_images/dmn/dmn-decision-edit.png

@@ -59,6 +59,8 @@ include::DMN/dmn-included-models-dmn-proc.adoc[leveloffset=+3]
 
 include::DMN/dmn-included-models-pmml-proc.adoc[leveloffset=+3]
 
+include::DMN/dmn-model-creating-multiples-proc.adoc[leveloffset=+2]
+
 include::DMN/dmn-documentation-con.adoc[leveloffset=+2]
 
 include::DMN/dmn-designer-nav-ref.adoc[leveloffset=+2]

_images/dmn/dmn-drd-actions-rename.png

@@ -1,7 +1,7 @@
 [id='dmn-boxed-expressions-con_{context}']
 = DMN decision logic in boxed expressions
 
-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) or decision requirements graph (DRG). 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 with one or more DRGs 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.
+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.
 
 The following are the types of DMN boxed expressions:
 

_images/dmn/dmn-drd-actions.png

@@ -1,7 +1,7 @@
 [id='dmn-drd-components-ref_{context}']
 = DMN decision requirements diagram (DRD) components
 
-A decision requirements diagram (DRD) is a visual representation of your DMN model. This diagram consists of one or more decision requirements graphs (DRGs) that represent a particular domain of an overall DRD. The DRGs trace business decisions using decision nodes, business knowledge models, sources of business knowledge, input data, and decision services.
+A decision requirements diagram (DRD) is a visual representation of your DMN model. A DRD can represent part or all of the overall decision requirements graph (DRG) for the DMN model. DRDs trace business decisions using decision nodes, business knowledge models, sources of business knowledge, input data, and decision services.
 
 The following table summarizes the components in a DRD:
 

_images/dmn/dmn-drd-multiple-back-end-details.png

@@ -1,7 +1,7 @@
 [id='dmn-logic-defining-proc_{context}']
 = Defining DMN decision logic in boxed expressions in {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) or decision requirements graph (DRG). 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 with one or more DRGs 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.
+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 {CENTRAL} to define decision logic for your DRD components using built-in boxed expressions.
 

_images/dmn/dmn-drd-multiple-back-end.png

@@ -0,0 +1,60 @@
+[id='dmn-model-creating-multiples-proc_{context}']
+= Creating DMN models with multiple diagrams in {CENTRAL}
+
+For complex DMN models, you can use the DMN designer in {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 {CENTRAL}. For information about creating DRDs, see xref:dmn-model-creating-proc_dmn-models[].
+
+.Procedure
+. In {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.
++
+--
+.DRD actions icon for subdividing a DRD
+image::dmn/dmn-drd-actions.png[]
+
+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.
+
+.Rename new nested DRD in the Decision Navigator menu
+image::dmn/dmn-drd-actions-rename.png[]
+--
+. 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.
+
+.Single DRD for loan prequalification
+image::dmn/dmn-example-drd.png[]
+
+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:
+
+.Multiple nested DRDs for loan prequalification
+image::dmn/dmn-drd-multiple.png[]
+
+.Overview of front end ratio DRD
+image::dmn/dmn-drd-multiple-front-end.png[]
+
+.DRD for front end ratio
+image::dmn/dmn-drd-multiple-front-end-details.png[]
+
+.Overview of credit score rating DRD
+image::dmn/dmn-drd-multiple-credit-score.png[]
+
+.DRD for credit score rating
+image::dmn/dmn-drd-multiple-credit-score-details.png[]
+
+.Overview of back end ratio DRD
+image::dmn/dmn-drd-multiple-back-end.png[]
+
+.DRD for back end ratio
+image::dmn/dmn-drd-multiple-back-end-details.png[]
+--

_images/dmn/dmn-drd-multiple-credit-score-details.png

@@ -5,6 +5,10 @@
 //IMPORTANT: For 7.24 and later, use the following include format:
 //include::ReleaseNotes/ReleaseNotesDrools.7.24.0.Final/ReleaseNotesDrools.7.24.0.Final-section.adoc[leveloffset=+1]
 //include::{shared-dir}/Workbench/ReleaseNotes/ReleaseNotesWorkbench.7.24.0.Final/ReleaseNotesWorkbench.7.24.0.Final-section.adoc[leveloffset=+1]
+
+
+include::{shared-dir}/Workbench/ReleaseNotes/ReleaseNotesWorkbench.7.44.0.Final/ReleaseNotesWorkbench.7.44.0.Final-section.adoc[leveloffset=+1]
+
 include::ReleaseNotes/ReleaseNotesDrools.7.41.0.Final/ReleaseNotesDrools.7.41.0.Final-section.adoc[leveloffset=+1]
 
 include::{shared-dir}/Workbench/ReleaseNotes/ReleaseNotesWorkbench.7.41.0.Final/ReleaseNotesWorkbench.7.41.0.Final-section.adoc[leveloffset=+1]

_images/dmn/dmn-drd-multiple-credit-score.png

@@ -24,7 +24,7 @@ The following table highlights the main decision-authoring assets supported in {
 |Decision Model and Notation (DMN) models
 a|
 * Are decision models based on a notation standard defined by the Object Management Group (OMG)
-* Use graphical decision requirements diagrams (DRDs) with one or more decision requirements graphs (DRGs) to trace business decision flows
+* Use graphical decision requirements diagrams (DRDs) that represent part or all of the overall decision requirements graph (DRG) to trace business decision flows
 * Use an XML schema that allows the DMN models to be shared between DMN-compliant platforms
 * Support Friendly Enough Expression Language (FEEL) to define decision logic in DMN decision tables and other DMN boxed expressions
 ifdef::PAM,JBPM[]

_images/dmn/dmn-drd-multiple-front-end-details.png

@@ -0,0 +1,5 @@
+[id='drools.releasenotesworkbench.7.44.0.final']
+
+= New and Noteworthy in Business Central 7.44.0
+
+include::multiple-drds-support-con.adoc[leveloffset=+1]

_images/dmn/dmn-drd-multiple-front-end.png

@@ -0,0 +1,13 @@
+[id='multiple-drds-support-con']
+
+= Support for multiple diagrams in DMN models
+
+For complex DMN models, you can now use the DMN designer in {CENTRAL} to design multiple DMN decision requirements diagrams (DRDs) that represent parts of the overall decision requirements graph (DRG) for a DMN decision model. This improvement enables you to better organize DMN decision models with many decision requirements by dividing the model into smaller nested DRDs.
+
+For more information about creating DMN models with multiple diagrams, see
+ifdef::PAM,DM[]
+{URL_DEVELOPING_DECISION_SERVICES}#dmn-model-creating-multiples-proc_dmn-models[_{DMN_MODELS}_]
+endif::[]
+ifdef::JBPM,DROOLS,OP[]
+xref:dmn-model-creating-multiples-proc_dmn-models[].
+endif::[]