You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: supplementary_style_guide/glossary_terms_conventions/general_conventions/a.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -500,7 +500,7 @@ An Ansible task is a set of instructions to achieve a state defined, in its broa
500
500
501
501
[[asset]]
502
502
==== image:images/yes.png[yes] asset (noun)
503
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, an _asset_ is anything that can be stored as a version in the artifact repository. Assets can be business rules, packages, business processes, decision tables, fact models, or domain-specific language (DSL) files.
503
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, an _asset_ is anything that can be stored as a version in the artifact repository. Assets can be business rules, packages, business processes, decision tables, fact models, or domain-specific language (DSL) files.
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _backward chaining_ is a feature of the rule engine. The backward chaining process is often referred to as derivation queries. It is not as common compared to reactive systems because Red{nbsp}Hat JBoss BRMS is primarily reactive forward chaining, that is, it responds to changes in your data. The backward chaining added to the rule engine is for product-like derivations.
25
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _backward chaining_ is a feature of the rule engine. The backward chaining process is often referred to as derivation queries. It is not as common compared to reactive systems because Red{nbsp}Hat Decision Manager is primarily reactive forward chaining, that is, it responds to changes in your data. The backward chaining added to the rule engine is for product-like derivations.
26
26
27
27
*Use it*: yes
28
28
@@ -556,7 +556,7 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
556
556
557
557
[[business-central]]
558
558
==== image:images/yes.png[yes] Business Central (noun)
559
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _Business Central_ is a web-based user interface. It is the user interface for the business rules manager and has been combined with the core Drools engine and other tools. It enables a business user to manage rules in a multi-user environment and implement changes in a controlled fashion.
559
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _Business Central_ is a web-based user interface. It is the user interface for the business rules manager and has been combined with the core Drools engine and other tools. It enables a business user to manage rules in a multi-user environment and implement changes in a controlled fashion.
560
560
561
561
*Use it*: yes
562
562
@@ -578,7 +578,7 @@ Do not use "BIOS" as a generic term for computer firmware. Instead, write "firmw
578
578
579
579
[[business-resource-planner]]
580
580
==== image:images/yes.png[yes] Business Resource Planner (noun)
581
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _Business Resource Planner_ is a lightweight, embeddable, planning engine that optimizes planning problems. It helps Java TM programmers solve planning problems efficiently, and it combines optimization heuristics and metaheuristics with very efficient score calculations.
581
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _Business Resource Planner_ is a lightweight, embeddable, planning engine that optimizes planning problems. It helps Java TM programmers solve planning problems efficiently, and it combines optimization heuristics and metaheuristics with very efficient score calculations.
Copy file name to clipboardExpand all lines: supplementary_style_guide/glossary_terms_conventions/general_conventions/d.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ LZO compression and LZ4 compression are specific compression algorithms, so they
39
39
40
40
[[data-enumeration]]
41
41
==== image:images/yes.png[yes] data enumeration (noun)
42
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _data enumeration_ is an optional type of asset that can be configured to provide drop-down lists for the guided decision table editor.
42
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _data enumeration_ is an optional type of asset that can be configured to provide drop-down lists for the guided decision table editor.
43
43
44
44
*Use it*: yes
45
45
@@ -94,7 +94,7 @@ LZO compression and LZ4 compression are specific compression algorithms, so they
94
94
95
95
[[data-model]]
96
96
==== image:images/yes.png[yes] data model (noun)
97
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _data model_ is a model of a data object. A _data object_ is a custom complex data type, such as a `Person` object with data fields `Name`, `Address`, and `Date of Birth`.
97
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _data model_ is a model of a data object. A _data object_ is a custom complex data type, such as a `Person` object with data fields `Name`, `Address`, and `Date of Birth`.
98
98
99
99
*Use it*: yes
100
100
@@ -105,7 +105,7 @@ LZO compression and LZ4 compression are specific compression algorithms, so they
105
105
106
106
[[data-modeler]]
107
107
==== image:images/yes.png[yes] Data Modeler (noun)
108
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _Data Modeler_ is a built-in editor for creating facts or data objects as part of a project data model from Business Central. Data objects are custom data types implemented as Java objects. These custom data types can be used in any resource (such as a guided decision table) after they have been imported.
108
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _Data Modeler_ is a built-in editor for creating facts or data objects as part of a project data model from Business Central. Data objects are custom data types implemented as Java objects. These custom data types can be used in any resource (such as a guided decision table) after they have been imported.
109
109
110
110
*Use it*: yes
111
111
@@ -171,7 +171,7 @@ LZO compression and LZ4 compression are specific compression algorithms, so they
*Description*: A _decision table_ is a collection of rules stored in either a spreadsheet or in the Red{nbsp}Hat JBoss BRMS user interface.
174
+
*Description*: A _decision table_ is a collection of rules stored in either a spreadsheet or in the Red{nbsp}Hat Decision Manager user interface.
175
175
176
176
*Use it*: yes
177
177
@@ -681,7 +681,7 @@ Red{nbsp}Hat Directory Server conforms to LDAP standards.
681
681
682
682
[[drl]]
683
683
==== image:images/yes.png[yes] DRL (noun)
684
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _DRL_ is an abbreviation for the "Drools Rule Language", which is a file with the .drl extension. A DRL file stores technical rules as text and can be managed in the Red{nbsp}Hat JBoss BRMS user interface. A DRL file contains one or more rules.
684
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _DRL_ is an abbreviation for the "Drools Rule Language", which is a file with the .drl extension. A DRL file stores technical rules as text and can be managed in the Red{nbsp}Hat Decision Manager user interface. A DRL file contains one or more rules.
685
685
686
686
*Use it*: yes
687
687
@@ -692,7 +692,7 @@ Red{nbsp}Hat Directory Server conforms to LDAP standards.
*Description*: The _Drools Expert_ is a pattern matching-based rule engine that runs on Java EE application servers, Red{nbsp}Hat JBoss BRMS platform, or bundled with Java applications. It comprises an inference engine, a production memory, and a working memory. Rules are stored in the production memory, and the facts that the inference engine matches the rules against are stored in the working memory.
695
+
*Description*: The _Drools Expert_ is a pattern matching-based rule engine that runs on Java EE application servers, Red{nbsp}Hat Decision Manager platform, or bundled with Java applications. It comprises an inference engine, a production memory, and a working memory. Rules are stored in the production memory, and the facts that the inference engine matches the rules against are stored in the working memory.
696
696
697
697
*Use it*: yes
698
698
@@ -703,7 +703,7 @@ Red{nbsp}Hat Directory Server conforms to LDAP standards.
703
703
704
704
[[dsl]]
705
705
==== image:images/yes.png[yes] DSL (noun)
706
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _DSL_ is an abbreviation for "domain-specific language". DSL is used to create a rule language that is dedicated to your problem domain. A set of DSL definitions consists of transformations from DSL sentences to DRL constructs. These constructs let you use all of the underlying rule language and engine features. You can write rules in DSL rule (DSLR) files, which are translated into Drools Rule Language (DRL) files.
706
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _DSL_ is an abbreviation for "domain-specific language". DSL is used to create a rule language that is dedicated to your problem domain. A set of DSL definitions consists of transformations from DSL sentences to DRL constructs. These constructs let you use all of the underlying rule language and engine features. You can write rules in DSL rule (DSLR) files, which are translated into Drools Rule Language (DRL) files.
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _guided editor_ is an editor for creating and editing business rules. Rules edited in the guided editor use the Business Rules Language (BRL) format. The guided editor prompts users for input based on the object model of the rule being edited.
338
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _guided editor_ is an editor for creating and editing business rules. Rules edited in the guided editor use the Business Rules Language (BRL) format. The guided editor prompts users for input based on the object model of the rule being edited.
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _inference engine_ is a part of the Red{nbsp}Hat JBoss BRMS engine, which matches production facts and data to rules. It is often called the brain of a production rules system because it is able to scale to a large number of rules and facts. It makes inferences based on its existing knowledge and performs the actions based on what it infers from the information.
353
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _inference engine_ is a part of the Red{nbsp}Hat Decision Manager engine, which matches production facts and data to rules. It is often called the brain of a production rules system because it is able to scale to a large number of rules and facts. It makes inferences based on its existing knowledge and performs the actions based on what it infers from the information.
354
354
355
355
*Use it*: yes
356
356
@@ -591,7 +591,7 @@ _This feature can run only on Intel 64 processors_
591
591
592
592
[[intelligent-process-server]]
593
593
==== image:images/yes.png[yes] Intelligent Process Server (noun)
594
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _Intelligent Process Server_ is a standalone, out-of-the-box component that can be used to instantiate and execute rules and processes. The Intelligent Process Server is created as a WAR file that can be deployed on any web container.
594
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _Intelligent Process Server_ is a standalone, out-of-the-box component that can be used to instantiate and execute rules and processes. The Intelligent Process Server is created as a WAR file that can be deployed on any web container.
Copy file name to clipboardExpand all lines: supplementary_style_guide/glossary_terms_conventions/general_conventions/k.adoc
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -231,7 +231,7 @@ Do not capitalize the first letter.
231
231
232
232
[[kie]]
233
233
==== image:images/yes.png[yes] KIE (noun)
234
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, "KIE" is an abbreviation for "Knowledge Is Everything". _KIE_ is a knowledge solution for Red{nbsp}Hat JBoss BRMS and JBoss BPM Suite and is used for the generic parts of a unified API, such as building, deploying, and loading.
234
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, "KIE" is an abbreviation for "Knowledge Is Everything". _KIE_ is a knowledge solution for Red{nbsp}Hat Decision Manager and Red{nbsp}Hat Process Automation Manager and is used for the generic parts of a unified API, such as building, deploying, and loading.
235
235
236
236
*Use it*: yes
237
237
@@ -242,7 +242,7 @@ Do not capitalize the first letter.
242
242
243
243
[[kie-api]]
244
244
==== image:images/yes.png[yes] KIE API (noun)
245
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _KIE API_ is a knowledge-centric API, where rules and processes are first class citizens. "KIE" is used for the generic parts of unified API, such as building, deploying, and loading.
245
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _KIE API_ is a knowledge-centric API, where rules and processes are first class citizens. "KIE" is used for the generic parts of unified API, such as building, deploying, and loading.
246
246
247
247
*Use it*: yes
248
248
@@ -253,7 +253,7 @@ Do not capitalize the first letter.
253
253
254
254
[[kie-base]]
255
255
==== image:images/yes.png[yes] KIE base (noun)
256
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, the _KIE base_ is a repository of the application’s knowledge definitions. The name of the Java object is `KieBase`. It contains rules, processes, functions, and type models. A KIE base does not contain runtime data; instead KIE sessions are created from the `KieBase` into which data can be inserted and process instances started.
256
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, the _KIE base_ is a repository of the application’s knowledge definitions. The name of the Java object is `KieBase`. It contains rules, processes, functions, and type models. A KIE base does not contain runtime data; instead KIE sessions are created from the `KieBase` into which data can be inserted and process instances started.
257
257
258
258
*Use it*: yes
259
259
@@ -264,7 +264,7 @@ Do not capitalize the first letter.
264
264
265
265
[[kie-session]]
266
266
==== image:images/yes.png[yes] KIE session (noun)
267
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, a _KIE session_ stores runtime data created from a KIE base. The name of the Java object is `KieSession`. After the KIE base is loaded, a session can be created to interact with the engine. The session can then be used to start new processes and signal events.
267
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, a _KIE session_ stores runtime data created from a KIE base. The name of the Java object is `KieSession`. After the KIE base is loaded, a session can be created to interact with the engine. The session can then be used to start new processes and signal events.
268
268
269
269
*Use it*: yes
270
270
@@ -275,7 +275,7 @@ Do not capitalize the first letter.
275
275
276
276
[[kjar]]
277
277
==== image:images/yes.png[yes] KJAR (noun)
278
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _KJARs_ are simple jar files that include a descriptor for the KIE system to produce KieBase and KieSession. Red{nbsp}Hat JBoss BPM Suite provides a simplified and complete deployment mechanism that is based entirely on Apache Maven artifacts. The KJAR descriptor is represented as the `kmodule.xml` file.
278
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _KJARs_ are simple jar files that include a descriptor for the KIE system to produce KieBase and KieSession. Red{nbsp}Hat Process Automation Manager provides a simplified and complete deployment mechanism that is based entirely on Apache Maven artifacts. The KJAR descriptor is represented as the `kmodule.xml` file.
279
279
280
280
*Use it*: yes
281
281
@@ -297,7 +297,7 @@ Do not capitalize the first letter.
297
297
298
298
[[knowledge-store]]
299
299
==== image:images/yes.png[yes] knowledge store (noun)
300
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, _knowledge store_ is a centralized repository for your business knowledge. The knowledge store connects to the Git repository to store various knowledge assets and artifacts at a single location.
300
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, _knowledge store_ is a centralized repository for your business knowledge. The knowledge store connects to the Git repository to store various knowledge assets and artifacts at a single location.
Copy file name to clipboardExpand all lines: supplementary_style_guide/glossary_terms_conventions/general_conventions/o.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -480,7 +480,7 @@ Use Organization Administrator as a proper noun when referring to the Organizati
480
480
481
481
[[organizational-unit]]
482
482
==== image:images/yes.png[yes] organizational unit (noun)
483
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, an _organizational unit_ is a directory comprising repositories that store business assets.
483
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, an _organizational unit_ is a directory comprising repositories that store business assets.
Copy file name to clipboardExpand all lines: supplementary_style_guide/glossary_terms_conventions/general_conventions/p.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@
11
11
12
12
[[package]]
13
13
==== image:images/yes.png[yes] package (noun)
14
-
*Description*: In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, a _package_ is a deployable collection of assets. Rules and other assets must be collected into a package before they can be deployed. When a package is built, the assets contained in the package are validated and compiled into a deployable package.
14
+
*Description*: In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, a _package_ is a deployable collection of assets. Rules and other assets must be collected into a package before they can be deployed. When a package is built, the assets contained in the package are validated and compiled into a deployable package.
15
15
16
16
*Use it*: yes
17
17
@@ -528,7 +528,7 @@ Use "source node" for the node in the active cluster when discussing geo-replica
528
528
529
529
[[project]]
530
530
==== image:images/yes.png[yes] project (noun)
531
-
*Description*: (1) In Red{nbsp}Hat OpenShift, a _project_ corresponds to a Kubernetes namespace. They organize and group objects in the system, such as services and deployments, as well as provide security policies specific to those resources. (2) In Red{nbsp}Hat JBoss BRMS and Red{nbsp}Hat JBoss BPM Suite, a project is a container that comprises packages of assets (business processes, rules, work definitions, decision tables, fact models, data models, and DSLs) and is located in the knowledge repository. This container defines the properties of the KIE base and KIE session that are applied to its content. You can edit these entities in the project editor in Business Central.
531
+
*Description*: (1) In Red{nbsp}Hat OpenShift, a _project_ corresponds to a Kubernetes namespace. They organize and group objects in the system, such as services and deployments, as well as provide security policies specific to those resources. (2) In Red{nbsp}Hat Process Automation Manager and Red{nbsp}Hat Decision Manager, a project is a container that comprises packages of assets (business processes, rules, work definitions, decision tables, fact models, data models, and DSLs) and is located in the knowledge repository. This container defines the properties of the KIE base and KIE session that are applied to its content. You can edit these entities in the project editor in Business Central.
0 commit comments