BXMSDOC 2464 master Dev Studio with BA: Update with BA 7.0 content

docs/drools-docs/src/main/asciidoc/DMN/DroolsDMNSupport-section.adoc

@@ -9,10 +9,17 @@ From a platform perspective, DMN models are just another type of asset that can
 execute DMN models as well as any of the other supported assets (such as DRL files and native decision tables) from the same kjar. This enables users to always use the best tool for
 the job at hand. In fact, it is common to have BPMN models directly invoke DMN decision services from their decision task nodes.
 
+[#dmn_support_in_drools_itemdefinition]
+== DMN ItemDefinition and Drools code
+End-user of the Drools Kie DMN API can represent DMN ItemDefinition structural types in a DMNContext in two ways:
+
+* by representing the DMN ItemDefinition with a user-defined Java type: must be a valid JavaBeans pojo defining properties and getters for each of the components in the DMN ItemDefinition. If necessary, it is possible to leverage the `@FEELProperty` annotation for those getters representing a component name which would result in an invalid Java identifier.
+* by representing the DMN ItemDefinition with a `java.util.Map`: the maps needs to define the appropriate entries, with the keys corresponding to the components name in the DMN ItemDefinition.
+
 [#dmn_support_in_drools_details]
 == DMN Implementation Details
 
-The DMN specification defines both syntax and semantic for the models. Note that, there are a few bugs and ambiguities in the specifications. At the moment, there is no Technology Compatibility Kit (TCK) or official reference implementation for DMN v1.1, to resolve these ambiguities. A vendor neutral effort for a TCK is available https://agilepro.github.io/dmn-tck/index.html[here].
+The DMN specification defines both syntax and semantic for the models. Note that, there are a few bugs and ambiguities in the specifications. At the moment, there is no Technology Compatibility Kit (TCK) or official reference implementation for DMN v1.1, to resolve these ambiguities. A vendor neutral effort for a TCK is available https://dmn-tck.github.io/tck[here].
 
 Drools strives to be as compliant as possible with the specification, however the following categories of differences exist:
 

docs/product-administration-and-configuration-guide/src/main/asciidoc/chap-integrating-red-hat-jboss-bpm-suite-with-red-hat-jboss-fuse.adoc

@@ -280,7 +280,7 @@ JBossFuse:karaf@root> features:install jbpm-workitems-camel
 
 == Configuring Dependencies
 
-When you configure KIE, Red Hat JBoss BRMS, or Red Hat Jboss BPM Suite in your application, you can follow one of the following approaches to build your OSGi application bundles:
+When you configure KIE, Red Hat JBoss BRMS, or Red Hat JBoss BPM Suite in your application, you can follow one of the following approaches to build your OSGi application bundles:
 
 * Bundle required dependencies into your application bundle. In this approach, you declare all required artifacts as runtime dependencies in your `pom.xml`. Hence, you need not import the packages that provide these artifacts that you have already added as dependencies.
 * Import the required dependencies into the application bundle. This is a preferred approach for building OSGi bundles as it adheres to the principles of OSGi framework. In this approach, you declare only the  API JARs (such as `org.kie:kie-api`) as dependencies in your application bundle. You will need to install the required Red Hat JBoss BRMS and Red Hat JBoss BPM Suite bundles and then import them in your application.

docs/product-administration-and-configuration-guide/src/main/asciidoc/chap-integrating-red-hat-jboss-brms-with-red-hat-jboss-fuse.adoc

@@ -255,7 +255,7 @@ JBossFuse:karaf@root> features:install jbpm-workitems-camel
 
 == Configuring Dependencies
 
-When you configure KIE, Red Hat JBoss BRMS, or Red Hat Jboss BPM Suite in your application, you can follow one of the following approaches to build your OSGi application bundles:
+When you configure KIE, Red Hat JBoss BRMS, or Red Hat JBoss BPM Suite in your application, you can follow one of the following approaches to build your OSGi application bundles:
 
 * Bundle required dependencies into your application bundle. In this approach, you declare all required artifacts as runtime dependencies in your `pom.xml`. Hence, you need not import the packages that provide these artifacts that you have already added as dependencies.
 

docs/product-assembly_business-processes/src/main/asciidoc/main.adoc

@@ -9,7 +9,7 @@ include::product-shared-docs/document-attributes.adoc[]
 include::product-shared-docs/author-group.adoc[]
 
 // Purpose statement for the assembly
-As a business analyst, you can use {CENTRAL} in {PRODUCT} to design a variety of business processes. A business process is a graph that describes the order in which a series of steps must be executed using a flow chart.
+As a citizen developer who wants to build rule-based solutions quickly, you can use {CENTRAL} in {PRODUCT} to design a variety of business processes. A business process is a graph that describes the order in which a series of steps must be executed using a flow chart.
 A process consists of a collection of predefined node types that are linked to each other using connections.
 Each of the nodes represents one step in the overall process while the connections specify how to transition from one node to the other.
 

docs/product-assembly_dmn-models/src/main/asciidoc/dm/master-docinfo.xml → docs/product-assembly_integrating-dev-studio/src/main/asciidoc/dm/master-docinfo.xml

@@ -5,6 +5,6 @@
 
 </subtitle>
 <abstract>
-	<para>This document describes how to design a decision service using Decision Model and Notation (DMN) models in {PRODUCT} {PRODUCT_VERSION}.</para>
+	<para>This document describes how to design a decision service using guided decision tables in {PRODUCT} {PRODUCT_VERSION}.</para>
 </abstract>
 <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

docs/product-assembly_integrating-dev-studio/src/main/asciidoc/main.adoc

@@ -0,0 +1,30 @@
+[id='assembly_integrating-dev-studio']
+
+include::product-shared-docs/document-attributes.adoc[]
+
+= Integrating JBoss Developer Studio with {PRODUCT} - BETA DRAFT
+// Context attribute is assembly specific and enables module reuse between assemblies.
+:imagesdir: topics/product-shared-docs/images
+:context: guided-decision-tables
+include::product-shared-docs/author-group.adoc[]
+
+// Purpose statement for the assembly
+As a developer, you can integrate JBoss Developer Studio with {PRODUCT} to write complex applications and leverage code auto-completion.
+
+//include::product-installation-guide/dev-studio-con.adoc[leveloffset=+1]
+include::product-development-guide/dev-studio-install-proc.adoc[leveloffset=+1]
+include::product-development-guide/dev-studio-plug-in-install-proc.adoc[leveloffset=+1]
+include::product-development-guide/dm-server-configure-proc.adoc[leveloffset=+1]
+include::product-development-guide/dev-studio-import-projects-from-git-repo-con.adoc[leveloffset=+1]
+include::product-development-guide/dev-studio-clone-remote-git-repo-proc.adoc[leveloffset=+2]
+include::product-development-guide/dev-studio-import-local-git-repo-proc.adoc[leveloffset=+2]
+
+== Next Steps
+For more information about using JBoss Developer Studio, see the following documents:
+
+* https://access.redhat.com/documentation/en-us/red_hat_jboss_developer_studio/11.3/html-single/getting_started_with_container_and_cloud-based_development/[Getting Started with Container and Cloud-based Development]
+* https://access.redhat.com/documentation/en-us/red_hat_jboss_developer_studio/11.3/html-single/getting_started_with_jboss_developer_studio_tools/[Getting Started with JBoss Developer Studio Tools]
+
+
+// Versioning info
+include::product-shared-docs/versioning-information.adoc[]

docs/product-assembly_decision-manager/src/main/asciidoc/dm/master-docinfo.xml → docs/product-assembly_integrating-dev-studio/src/main/asciidoc/pam/master-docinfo.xml

@@ -5,6 +5,6 @@
 
 </subtitle>
 <abstract>
-	<para>In this tutorial, you will create and test a driver's license suspension scenario.</para>
+	<para>This document describes how to integrate Red Hat JBoss Developer Studio with {PRODUCT}.</para>
 </abstract>
 <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

docs/product-assembly_migrating-6.4-to-7.x/src/main/asciidoc/main.adoc

@@ -87,6 +87,12 @@ include::product-migration-guide/migration-planner-changes-ref.adoc[leveloffset=
 == Next steps
 * {URL_GETTING_STARTED_DECISION_SERVICE}[_{GETTING_STARTED_DECISION_SERVICE}_]
 * {URL_GUIDED_DECISION_TABLES}[_{GUIDED_DECISION_TABLES}_]
+ifdef::PAM[]
+* _Getting started with business processes_ (link coming soon)
+* _Modeling a new business process_ (link coming soon)
+endif::PAM[]
+//@link: Add links for process docs above.
+
 
 // Versioning info
 include::product-shared-docs/versioning-information.adoc[]

docs/product-development-guide/src/main/asciidoc/chap-remote-api.adoc

@@ -1916,7 +1916,7 @@ public class DocumentationJmsExamples {
     int loompaMonitoringResultIndex = 1;
     // 5
     // Get JNDI context from server:
-    InitialContext context = getRemoteJbossInitialContext(serverUrl, USER, PASSWORD);
+    InitialContext context = getRemoteJBossInitialContext(serverUrl, USER, PASSWORD);
 
     // Create JMS connection:
     ConnectionFactory connectionFactory;
@@ -2082,7 +2082,7 @@ public class DocumentationJmsExamples {
     return cmdResponses;
   }
 
-  private InitialContext getRemoteJbossInitialContext(URL url, String user, String password) {
+  private InitialContext getRemoteJBossInitialContext(URL url, String user, String password) {
 
     Properties initialProps = new Properties();
     initialProps.setProperty(InitialContext.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
@@ -2662,7 +2662,7 @@ Sets the JMS queue for requests related to the task service usage.
 addResponseQueue(javax.jms.Queue param)::
 Sets a JMS queue used for receiving responses.
 
-addJbossServerHostName(String param)::
+addJBossServerHostName(String param)::
 Sets a host name to look up and retrieve a remote instance of `InitialContext`.
 
 addHostName(String param)::
@@ -2723,7 +2723,7 @@ public class RemoteJavaApiJmsClientExample {
       RuntimeEngine engine = RemoteRuntimeEngineFactory
         .newJmsBuilder()
         .addDeploymentId(deploymentId)
-        .addJbossServerHostName(serverUrl.getHost())
+        .addJBossServerHostName(serverUrl.getHost())
         .addUserName(user)
         .addPassword(password)
         .build();
@@ -2749,7 +2749,7 @@ When configuring the `RemoteJmsRuntimeEngineBuilder` with an `InitialContext` in
 
 [source,java]
 ----
-private InitialContext getRemoteJbossInitialContext(URL url, String user, String password) {
+private InitialContext getRemoteJBossInitialContext(URL url, String user, String password) {
 
   Properties initialProps = new Properties();
   initialProps.setProperty(InitialContext.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");

docs/product-development-guide/src/main/asciidoc/dev-studio-clone-remote-git-repo-proc.adoc

@@ -2,12 +2,13 @@
 = Cloning a remote Git repository
 You can clone a git repository to use with Red Hat JBoss Developer Studio.
 
-.Prerequisite
-Access permission for the remote Git repository that you want to clone
+.Prerequisites
+* Red Hat JBoss Developer Studio is installed with the {PRODUCT} plug-ins.
+* You have access permission for the remote Git repository that you want to clone.
 
 .Procedure
-. In Red Hat JBoss Developer Studio, select the server from the *Server* tab and click the start icon to start your server.
-. Enter the following command in a terminal to start the Secure Shell server, if it is not running already. 
+. In Red Hat JBoss Developer Studio, to start your server, select the server from the *Server* tab and click the start icon.
+. Enter the following command in a terminal to start the secure shell server, if it is not running already. 
 +
 [source]
 ----
@@ -18,10 +19,11 @@ Access permission for the remote Git repository that you want to clone
 ====
 This command is specific to Linux and Apple Macintosh. On these platforms, if `sshd` has already been started, this command fails. If this happens, you may safely ignore this step.
 ====
-. In Red Hat JBoss Developer Studio , select *File* -> *Import...* and navigate to the Git folder. Open the Git folder to select *Projects from Git* and click *Next*.
+. In Red Hat JBoss Developer Studio , select *File* -> *Import...* and navigate to the Git folder. 
+. Open the Git folder, select *Projects from Git*, and click *Next*.
 . Select the repository source as *Clone URI* and click *Next*.
-. Enter the details of the Git repository in the next window and click *Next*.
-. Select the branch you wish to import in the following window and click *Next*.
-. To define the local storage for this project, enter (or select) a non-empty directory, make any configuration changes and click *Next*.
+. Enter the details of the Git repository and click *Next*.
+. Select the branch you want to import and click *Next*.
+. To define the local storage for this project, enter or select a non-empty directory, make any configuration changes, and click *Next*.
 . Import the project as a general project in the following window and click *Next*.
 . Name the project and click *Finish*.

docs/product-development-guide/src/main/asciidoc/dev-studio-import-local-git-repo-proc.adoc

@@ -2,10 +2,13 @@
 = Importing a local Git repository
 You can import a local git repository to use with Red Hat JBoss Developer Studio.
 
+.Prerequisite
+Red Hat JBoss Developer Studio is installed.
+
 .Procedure
-. Select your server from the *Server* tab and click the start icon to start the server.
-. In Red Hat JBoss Developer Studio, select *File* -> *Import...* and navigate to the Git folder. Open the Git folder to select *Projects from Git* and click *Next*.
+. In Red Hat JBoss Developer Studio, to start your server, select the server from the *Server* tab and click the start icon.
+. Select *File* -> *Import...* and navigate to the Git folder. Open the Git folder to select *Projects from Git* and click *Next*.
 . Select the repository source as *Existing local repository* and click *Next*.
 . Select the repository that is to be configured from the list of available repositories and click *Next*.
-. In the dialog window that opens, select the *Import as general project* radio button from the *Wizard for project import* group and click *Next*.
+. In the window that opens, select *Import as general project* and click *Next*.
 . Name the project and click *Finish*.

docs/product-development-guide/src/main/asciidoc/dev-studio-import-projects-from-git-repo-con.adoc

@@ -1,6 +1,4 @@
 [id='dev-studio-import-projects-from-git-repo']
 = Importing projects from a Git repository into Red Hat JBoss Developer Studio
 
-You can configure Red Hat JBoss Developer Studio to connect to a central Git asset repository. The repository stores rules, models, functions, and processes.
-
-You can either clone a remote Git repository or import a local Git repository.
+You can configure Red Hat JBoss Developer Studio to connect to a central Git asset repository. The repository stores rules, models, functions, and processes. You can either clone a remote Git repository or import a local Git repository.