diff --git a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-custom-datatypes-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-custom-datatypes-proc.adoc index d67efe3f71..4c4625db19 100644 --- a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-custom-datatypes-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-custom-datatypes-proc.adoc @@ -4,12 +4,7 @@ DMN data types determine the structure of the data that you use within a table, column, or field in a DMN boxed expression for defining decision logic. You can use default DMN data types (such as string, number, or boolean) or you can create custom data types to specify additional fields and constraints that you want to implement for the boxed expression values. Use the DMN designer's *Data Types* tab in {CENTRAL} to define the custom data types for the traffic violations project. .The custom data types tab -image::dmn/dmn-custom-datatypes-tab.png[] - -//Alternately, you can also access the *Data Types* tab from the *Properties* tab on the right. From the *Properties* tab, click *Manage* from *Data type* under *Information item*. - -//.Diagram properties tab -//image::dmn/dmn-diagram-properties-tab.png[] +image::dmn/dmn-custom-datatypes-tab.png[The custom data types tab] The following tables list the `tDriver`, `tViolation`, and `tFine` custom data types that you will create for this project. @@ -57,7 +52,7 @@ The following tables list the `tDriver`, `tViolation`, and `tFine` custom data t . Click the check mark to the right of the new data type to save your changes. + .The tDriver custom data type -image::dmn/dmn-tDriver-custom-datatype.png[] +image::dmn/dmn-tDriver-custom-datatype.png[The tDriver custom data type] . Add each of the following nested data types to the `tDriver` structured data type by clicking the plus sign next to `tDriver` for each new nested data type. Click the check mark to the right of each new data type to save your changes. + * `Name` (string) @@ -70,7 +65,7 @@ image::dmn/dmn-tDriver-custom-datatype.png[] . Click the check mark to the right of the new data type to save your changes. + .The tViolation custom data type -image::dmn/dmn-tViolation-custom-datatype.png[] +image::dmn/dmn-tViolation-custom-datatype.png[The tViolation custom data type] . Add each of the following nested data types to the `tViolation` structured data type by clicking the plus sign next to `tViolation` for each new nested data type. Click the check mark to the right of each new data type to save your changes. + * `Code` (string) @@ -89,7 +84,7 @@ image::dmn/dmn-tViolation-custom-datatype.png[] . To create the `tFine` custom data type, click *New Data Type*, enter `tFine` in the *Name* field, select `Structure` from the *Type* list, and click *Save*. + .The tFine custom data type -image::dmn/dmn-tFine-custom-datatype.png[] +image::dmn/dmn-tFine-custom-datatype.png[The tFine custom data type] . Add each of the following nested data types to the `tFine` structured data type by clicking the plus sign next to `tFine` for each new nested data type. Click the check mark to the right of each new data type to save your changes. + * `Amount` (number) diff --git a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-drd-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-drd-proc.adoc index 6c801cb7b7..8f9d254487 100644 --- a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-drd-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-creating-drd-proc.adoc @@ -4,7 +4,7 @@ A decision requirements diagram (DRD) is a visual representation of your DMN model. Use the DMN designer in {CENTRAL} to design the DRD for the traffic violations project and to define the decision logic of the DRD components. .DRD for the Traffic Violations example -image::dmn/dmn-traffic-violations-drd.png[] +image::dmn/dmn-traffic-violations-drd.png[DRD for the Traffic Violations example] .Prerequisites * You have created the traffic violations project in {CENTRAL}. @@ -19,9 +19,9 @@ image::dmn/dmn-traffic-violations-drd.png[] + .DMN Input Data nodes -image::dmn/library_objects.png[] +image::dmn/library_objects.png[DMN Input Data nodes] -. In the upper-right corner, click the image:getting-started/diagram_properties.png[] icon. +. In the upper-right corner, click the image:getting-started/diagram_properties.png[Properties] icon. . Double-click the input nodes and rename one to `Driver` and the other to `Violation`. . Drag a *DMN Decision* decision node onto the canvas. . Double-click the decision node and rename it to `Fine`. @@ -29,7 +29,7 @@ image::dmn/library_objects.png[] + .Create DMN Information Requirement icon -image::dmn/info-requirement.png[] +image::dmn/info-requirement.png[Create DMN Information Requirement icon] . Drag a *DMN Decision* decision node onto the canvas. . Double-click the decision node and rename it to `Should the driver be suspended?`. diff --git a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-defining-decision-logic-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-defining-decision-logic-proc.adoc index aa8e8a5c9a..d043f23e8a 100644 --- a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-defining-decision-logic-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-defining-decision-logic-proc.adoc @@ -4,10 +4,10 @@ To calculate the fine and to decide whether the driver is to be suspended or not, you can define the traffic violations DMN decision logic using a DMN decision table and context boxed expression. .Fine expression -image::dmn/dmn-gs-fine-decision-table.png[] +image::dmn/dmn-gs-fine-decision-table.png[Fine expression decision table] .Should the driver be suspended expression -image::dmn/dmn-gs-context-table.png[] +image::dmn/dmn-gs-context-table.png[Should the driver be suspended expression decision table] .Prerequisites * You have assigned the DMN custom data types to the appropriate decision and input nodes in the traffic violations DRD in {CENTRAL}. @@ -17,13 +17,13 @@ image::dmn/dmn-gs-context-table.png[] + .Decision node edit icon -image::dmn/decision_node_edit.png[] +image::dmn/decision_node_edit.png[Decision node edit icon] . Click *Select expression* -> *Decision Table*. + .Select Decisiong Table logic type -image::dmn/select_logic_type.png[] +image::dmn/select_logic_type.png[Select logic type menu] . For the *Violation.Date*, *Violation.Code*, and *Violation.Speed Limit* columns, right-click and select *Delete* for each field. . Click the *Violation.Actual Speed* column header and enter the expression `Violation.Actual Speed - Violation.Speed Limit` in the *Expression* field." diff --git a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-new-project-creating-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-new-project-creating-proc.adoc index 029209b4c7..37c3e5d66a 100644 --- a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-new-project-creating-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-new-project-creating-proc.adoc @@ -6,19 +6,13 @@ For this example, create a new project called `traffic-violation`. A project is .Procedure . In {CENTRAL}, go to *Menu* -> *Design* -> *Projects*. + - -{PRODUCT} provides a default space called *MySpace*, as shown in the following image. You can use the default space to create and test example projects. -+ - -.Default space -image::getting-started/spaces-teams.png[] - +{PRODUCT} provides a default space called *MySpace*. You can use the default space to create and test example projects. . Click *Add Project*. . Enter `traffic-violation` in the *Name* field. . Click *Add*. + .Add Project window -image::dmn/dmn-new-project-gs.png[] +image::dmn/dmn-new-project-gs.png[Add project window] + The *Assets* view of the project opens. diff --git a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-testing-test-scenario-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-testing-test-scenario-proc.adoc index 35f76b3b09..61f1954dd9 100644 --- a/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-testing-test-scenario-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/DMN/dmn-gs-testing-test-scenario-proc.adoc @@ -4,7 +4,7 @@ Use the test scenarios designer in {CENTRAL} to test the DMN decision requirements diagrams (DRDs) and define decision logic for the traffic violations project. .Test scenario for the traffic violations example -image::dmn/dmn-gs-traffic-violation-test-scenarios.png[] +image::dmn/dmn-gs-traffic-violation-test-scenarios.png[Test scenario for the traffic violations example] .Prerequisites * You have successfully built the traffic violations project in {CENTRAL}. @@ -76,9 +76,6 @@ Right-click the fourth row and select *Insert row below* to add another row. . Click the *Play* icon image:dmn/dmn-play-icon.png[] to check whether the test scenarios pass or fail. + .Test scenario execution result for the traffic violations example -image::dmn/dmn-gs-test-scenarios-execution-results.png[] +image::dmn/dmn-gs-test-scenarios-execution-results.png[Test scenario execution result for the traffic violations example] + In case of failure, correct the errors and run the test scenarios again. - -//.DRD for the Traffic Violation example -//image::dmn/dmn-traffic-violations-drd.png[] diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc index 9067a0ef9a..b2d22e0854 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc @@ -5,4 +5,4 @@ A business process is a diagram that describes the order in which a series of st The sample *Mortgage_Process* contains the following predefined *MortgageApprovalProcess* business process. -image:getting-started/sampleBP.png[] +image:getting-started/sampleBP.png[screen capture of the mortgageApprovalProcess business process] diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc index 6b6165637a..0b3e43f705 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc @@ -15,7 +15,7 @@ The *Package* specifies the location inside the existing project where the asset . Click *Ok*. The diagram editor opens. . In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[] in the *Process Variables* section. +. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[the plus sign icon] in the *Process Variables* section. . Enter the following values: + * *Name*: `application` @@ -26,23 +26,23 @@ This section shows you how to create outgoing connections, exclusive gateways, a {PRODUCT} contains a predefined selection of node types to simplify business process creation. The predefined node panel is located on the left side of the diagram editor. -image:getting-started/node_panel.png[] +image:getting-started/node_panel.png[screen capture of the node panel] .Procedure . Drag a start event node onto the canvas. . Create an outgoing connection from the start event to an exclusive gateway: .. On the canvas, click the start event node and click the *Create Parallel* icon. + -image::getting-started/create-parallel.png[] +image::getting-started/create-parallel.png[screen capture of the event node and the Create Parallel icon] .. Hover over the image:getting-started/config-icon.png[] icon of the parallel and click the *Convert into Exclusive* icon. + -image::getting-started/exclusive-gateway.png[] +image::getting-started/exclusive-gateway.png[screen capture of the event node and the Convert into Exclusive icon] . Create an outgoing connection from the exclusive gateway to a business rule task: .. On the canvas, click the exclusive gateway and click the *Create Task* icon. .. Hover over the image:getting-started/config-icon.png[] icon of the task and click the *Convert into Business Rule* icon. + -image::getting-started/bus-rule-task.png[] +image::getting-started/bus-rule-task.png[screen capture of the Convert into Business Rule icon] . Configure the business rule task: @@ -56,7 +56,7 @@ image::getting-started/bus-rule-task.png[] ---- System.out.println(application.getProperty()); ---- -.. Expand *Data Assignments* and click image:getting-started/btn_assign.png[] next to *Assignments*. +.. Expand *Data Assignments* and click image:getting-started/btn_assign.png[the Assign icon] next to *Assignments*. .. In the *Validation Data I/O* window, click *Add* and create the following assignments: * Data Inputs and Assignements ** Name: application @@ -82,14 +82,14 @@ This section shows you how to define the validation data that determines whether .. Click the *Validation* task and click the *Create Parallel* icon. .. Hover over the image:getting-started/config-icon.png[] icon of the parallel and click the *Convert into Exclusive* icon. + -image::getting-started/exclusive_gateway.png[] +image::getting-started/exclusive_gateway.png[screen capture of the Convert into Exclusive icon] . Create an outgoing connection from the exclusive gateway to a new business rule task: .. Click the exclusive gateway and click the *Create Task* icon. .. Drag the new task below the exclusive gateway as shown in the following image. .. Hover over the image:getting-started/config-icon.png[] icon of the task and click the *Convert into Business Rule* icon. + -image::getting-started/new_br_task.png[] +image::getting-started/new_br_task.png[screen capture of the Increase Down Payment Data I/O] .. If the *Properties* panel is not open, click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. .. In the *Properties* panel, enter `Retract Validation` in the *Name* field. .. Expand *Implementation/Execution*, select *New* from the *Rule Flow Group* menu, and input `error`. @@ -97,24 +97,24 @@ image::getting-started/new_br_task.png[] . Configure the connection between the exclusive gateway and the business rule task: .. Click the connection. + -image::getting-started/created-connection.png[] +image::getting-started/created-connection.png[screen capture of the business process with connections] .. If the *Properties* panel is not open, click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. .. In the *Properties* panel, enter `Invalid` in the *Name* field. .. Expand *Implementation/Execution* and select *Expression* in the *Condition Expression* section. .. From the list, select *drools* and enter `ValidationErrorDO()` in the *Condition Expression* field. + -image::getting-started/languagedropdown.png[] +image::getting-started/languagedropdown.png[screen capture of the Condition Expression dialog] . Create an outgoing connection from the *Retract Validation* task to a new user task: .. Click the *Retract Validation* task and click the *Create Task* icon. .. Drag the new task below the *Validation* task as shown below. .. Hover over the image:getting-started/config-icon.png[] icon of the task and click the *Convert into User* icon. + -image::getting-started/user_task.png[] +image::getting-started/user_task.png[screen capture of the business process and the Convert into User icon] .. Click the new user task and in the *Properties* panel, enter `Correct Data` in the *Name* field. .. Expand *Implementation/Execution* and enter `CorrectData` in the *Task Name* field. .. Select *New* from the *Groups* menu, and input `broker`. -.. Click image:getting-started/btn_assign.png[] next to *Assignments*. +.. Click image:getting-started/btn_assign.png[the Assign icon] next to *Assignments*. .. In the *Correct Data Data I/O* window, click *Add* and create the following assignments: ** Name: application ** Data Type: Application [com.myspace.mortgage_app] @@ -131,7 +131,7 @@ image::getting-started/correct-data-io.png[Screen capture of the Correct Data Da . Click the *Correct Data* user task then click the *Create sequence Flow* icon and drag it back to the first exclusive gateway. Your workflow should look similar to the following diagram: + -image::getting-started/workflow1.png[] +image::getting-started/workflow1.png[screen capture of the completed business process] == Calculating the mortgage The mortgage calculation business process determines the applicant's mortgage borrowing limit. @@ -143,16 +143,17 @@ The mortgage calculation business process determines the applicant's mortgage bo .. From the list, select *drools* and enter `not ValidationErrorDO()` in the *Condition Expression* field. . Click the new business rule task and in the *Properties* panel, input `Mortgage Calculation` in the *Name* field. + -image::getting-started/validconnection.png[] +image::getting-started/validconnection.png[screen capture of the business process] .. Expand *Implementation/Execution*, select *New* from the *Rule Flow Group* menu, and input `mortgagecalculation`. -. Expand *Data Assignments* and click image:getting-started/btn_assign.png[] next to *Assignments*. +. Expand *Data Assignments* and click image:getting-started/btn_assign.png[the Assign icon] next to *Assignments*. . In the *Mortgage Calculation Data I/O* window, click *Add* to create the following assignments and click *Save*. + + .Mortgage Calculation Data I/O assignments image::getting-started/mortgage-calc-assignments.png[screen capture of the Mortgage Calculation Data I/O assignments] -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: * *Name*: `inlimit` * *Data Type*: `Boolean` @@ -161,7 +162,7 @@ image::getting-started/mortgage-calc-assignments.png[screen capture of the Mortg . Click the user task, enter `Qualify` in the *Name* field. . Expand *Implementation/Execution* and enter `Qualify` in the *Task Name* field. . Select *New* from the *Groups* menu, and input `approver`. -. Click image:getting-started/btn_assign.png[] next to *Assignments*. In the *Qualify Data I/O* window, click *Add* to create the following assignments: +. Click image:getting-started/btn_assign.png[the Assign icon] next to *Assignments*. In the *Qualify Data I/O* window, click *Add* to create the following assignments: + .Qualify Data I/O assignments image::getting-started/qualify-io.png[Screen capture of the Qualify Data I/O assignments] @@ -174,12 +175,12 @@ image::getting-started/qualify-io.png[Screen capture of the Qualify Data I/O ass . Expand *Implementation/Execution* and select *Condition* in the *Condition Expression* section. . Select *inlimit* from the *Process Variable* drop-down menu and select *Is true* from the *Condition* drop-down menu. + -image::getting-started/inlimit-true.png[] +image::getting-started/inlimit-true.png[screen caputure of the expanded Implementation/Execution panel] . Click the user task, enter `Final Approval` in the *Name* field. . Expand *Implementation/Execution* and enter `FinalApproval` in the *Task Name* field. . Select *New* from the *Groups* menu, and input `manager`. -. Click image:getting-started/btn_assign.png[] next to *Assignments*. In the *Final Approval Data I/O* window, click *Add* to create the following assignments: +. Click image:getting-started/btn_assign.png[the Assign icon] next to *Assignments*. In the *Final Approval Data I/O* window, click *Add* to create the following assignments: + .Final Approval Data I/O assignments image::getting-started/approval-io.png[Screen capture of the Final Approval Data I/O assignments] @@ -193,26 +194,26 @@ The Increasing the Down Payment business process checks to see if the applicant . Click the *Final Approval* user task and select *Create End* from the user task quick menu. . Move the end event below the *Final Approval* user task. + -image::getting-started/create_end.png[] +image::getting-started/create_end.png[screen capture of the Final Approval user task and end event] . Return to the exclusive gateway that connects with the *Final Approval* user task. Create a second outgoing connection and connect it to a new user task. + -image::getting-started/new-task.png[] +image::getting-started/new-task.png[screen capture of the business process and the second outgoing connection] . Click the connection and input `Not in Limit` in the *Name* field of the *Properties* panel. . Expand *Implementation/Execution* and select *Condition* in the *Condition Expression* section. . Select *inlimit* from the *Process Variable* drop-down menu and select *Is false* from the *Condition* drop-down menu. -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: + * *Name*: `incdownpayment` * *Data Type*: `Boolean` + -image::getting-started/proc-var-new.png[] +image::getting-started/proc-var-new.png[screen capture of the Process Data dialog] . Click the new user task and in the *Properties* panel, input `Increase Down Payment` in the *Name* field. . Expand *Implementation/Execution* and enter `IncreaseDownPayment` in the *Task Name* field. . Select *New* from the *Groups* menu, and input `broker`. -. Click image:getting-started/btn_assign.png[] next to *Assignments*. In the *Increase Down Payment Data I/O* window, click *Add* to create the following assignments: +. Click image:getting-started/btn_assign.png[the Assign icon] next to *Assignments*. In the *Increase Down Payment Data I/O* window, click *Add* to create the following assignments: + .Increase Down Payment Data I/O assignments image::getting-started/increase-down-io.png[Screen capture of the Increase Down Payment Data I/O assignments] diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc index 5de70d8b25..c062792373 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc @@ -11,7 +11,7 @@ Review the *WHEN* and *THEN* rules so that you understand how the conditions are . From the asset list, click the right arrow to view the second page of the asset list and click the *Validate Down Payment* guided rule. . Review the *Validate Down Payment* guided rule's *WHEN* and *THEN* conditions and values. + -image::getting-started/validate-rules.png[] +image::getting-started/validate-rules.png[screen caputure of the Validate Down Payment.drl Guided Rules dialog] == Viewing the *RetractValidationErr* guided rule Review the *WHEN* and *THEN* rules so that you understand how the conditions are set and used later when you run the process. diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/creating-users-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/creating-users-proc.adoc index b55b6dba99..c6b06c49fe 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/creating-users-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/creating-users-proc.adoc @@ -11,13 +11,13 @@ In {CENTRAL}, you can use groups and roles to control permissions for a collecti .Procedure . Click the gear icon image:project-data/gear-icon.png[] in the upper-right corner and click *Users*. -. Click image:Designer/new-user.png[], enter `Katy`, click *Next*, and click *Create*. +. Click image:Designer/new-user.png[new user], enter `Katy`, click *Next*, and click *Create*. . Click *Yes* to set a password, enter `Katy` in both fields, and click *Change*. . Enter `Bill`, click *Next*, and click *Create*. . Click *Yes* to set a password, enter `Bill` in both fields, and click *Change*. -. Click the *Groups* tab and click image:project-data/new_group.png[], enter `approver`, and click *Next* +. Click the *Groups* tab and click image:project-data/new_group.png[new group], enter `approver`, and click *Next* . Select `Katy` from the user list, and click *Add selected users*. -. Click image:project-data/new_group.png[], enter `broker`, and click *Next*. +. Click image:project-data/new_group.png[new group], enter `broker`, and click *Next*. . Select `Bill` from the user list, and click *Add selected users*. . Click *Users*, select `Katy`, and click *Edit* -> *Roles* -> *Add roles*. . Select `manager`, click *Add to selected roles*, and click *Save*. diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/decision-tables-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/decision-tables-proc.adoc index 24d94cc8fc..dc8daf0cb3 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/decision-tables-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/decision-tables-proc.adoc @@ -7,79 +7,7 @@ The goal of this chapter is to introduce you to the *MortgageDecisionTable* deci * The business rules have been defined. For more information, see <<_defining_business_rules>>. .Procedure -//. In {CENTRAL}, go to *Menu* -> *Design* -> *Projects*, and **Mortgage_Process**. -//. Click *Add Asset* -> *Guided Decision Table*, and enter the following values: - -//* *Name*: `Mortgage Decision Table` -//* *Package*: `com.myspace.mortgage_app` -//+ -//. Select *Use Wizard*. -//+ -//image::getting-started/table-wizard.png[] - -//. Click *Ok* to open the *Guided Decision Table Wizard*. -//+ -//image::getting-started/wizard-panel.png[] - -//== Setting the Mortgage Decision Table conditions -//You must set the table conditions that is used to determine the loan applicants eligibility. - -//. Select *Add Fact Patterns*. -//. Move the *Applicant* and *Property* patterns to the *Chosen patterns* section. -//. Click *Add Constraints*, select *Applicant > annualincome:Whole number (integer)*, and move *annualincome..* to the *Conditions* section. -//+ -//image::getting-started/income-condition.png[] - -//. From *Conditions*, select *annualincome*, and enter: -//+ -//* *Column header (description)*: `Annual Income (Greater Than)` -//* *Operator*: `greater than` -//+ -//. Move *annualincome:Whole number (integer)* to the *Conditions* section. -//. From *Conditions*, select *annualincome*, and enter: -//+ -//* *Column header (description)*: `Annual Income (Less Than or Equal To)` -//* *Operator*: `less than or equal to` -//+ -//. From *Available patterns*, select *Property*, and from *Available fields*, select *saleprice:Whole number (integer)* and move it to the *Conditions* section. -//. From *Conditions*, select *saleprice*, and enter: -//+ -//* *Column header (description)*: `Sale Price (Less Than)` -//* *Operator*: `less than` -//. From *Available fields*, select *age: Text*, and move it to the *Conditions* section. -//. From *Conditions*, select *age*, and enter: -//+ -//* *Column header (description)*: `Property Age (Less Than)` -//* *Operator*: `less than` -//. From *Available fields*, select *locale:Text*, and move it to the *Conditions* section. -//. From *Conditions*, select *locale*, and enter: -//+ -//* *Column header (description)*: `Location` -//* *Operator*: `equal to` -//* *(optional) value list*: `Urban,Rural` -//+ -//image::getting-started/conditions-final.png[] - -//. Click *Next*. - -//== Defining the Mortgage Decision Table actions -//Define the actions that are based on table conditions that you set in the previous chapter. - -//. Click *Add Actions to insert Facts*, select *Application* and move it to the *Chosen patterns* section. -//. Click *Application* to open the *Available fields*, select *mortgageamount:Whole number (integer)*, and move it to the *Chosen fields* section. -//. From *Chosen fields*, select *mortgageamount*. -//. Enter `Mortgage Amount` in the *Column header (description)* field and click *Finish*. -//. Click *Save*, and *Save*, to confirm your changes. -//. Click *Insert > Insert column*. -//+ -//image::getting-started/insert-col.png[] - -//. Select *Include advanced options*, and select *Add an Attribute column* and click *Next*. -//. Select *Ruleflow-group*, and click *Finish*. -//+ -//image::getting-started/rule-group.png[] - . In {CENTRAL}, go to *Menu* -> *Design* -> *Projects* -> *Mortgage_Process*. . Scroll down and click the *MortgageDecisionTable* Guided Decision Tables asset. + -image:getting-started/loans-guided-dt.png[] +image:getting-started/loans-guided-dt.png[screen capture of the MortgageDecisionTable Guided Decision Tables asset] diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc index eb6cfc0ddc..0702d3a8d4 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc @@ -28,7 +28,7 @@ Now that you have deployed the project, you can execute the project's defined fu . Click *Submit* to start a new process instance. After starting the process instance, the *Instance Details* view opens. . Click the *Diagram* tab to view the process flow within the process diagram. The state of the process is highlighted as it moves through each task. + -image::project-data/diagram-progress.png[] +image::project-data/diagram-progress.png[screen capture of the process flow within the process diagram] . Log out of {Central} and log back in as `Katy`. . Click *Menu* -> *Track* -> *Task Inbox*. This takes you to the *Qualify* form. diff --git a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/new-project-proc.adoc b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/new-project-proc.adoc index 28b45f6ebb..f53ee57a7f 100644 --- a/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/new-project-proc.adoc +++ b/doc-content/drools-docs/src/main/asciidoc/GettingStartedDecServices/new-project-proc.adoc @@ -7,12 +7,8 @@ A project is a container for assets such as data objects, business processes, gu . In {CENTRAL}, go to *Menu* -> *Design* -> *Projects*. + -{PRODUCT} provides a default space called *MySpace*, as shown in the following image. You can use the default space to create and test example projects. +{PRODUCT} provides a default space called *MySpace*. You can use the default space to create and test example projects. + - -.Default space -image::getting-started/spaces-teams.png[] - . Click *Add Project*. . Enter `mortgage-process` in the *Name* field. . Click *Configure Advanced Options* and modify the GAV fields with the following values: diff --git a/doc-content/enterprise-only/cases/case-management-assign-task-to-role-proc.adoc b/doc-content/enterprise-only/cases/case-management-assign-task-to-role-proc.adoc index 9432dedfa3..8e7cc3e0e8 100644 --- a/doc-content/enterprise-only/cases/case-management-assign-task-to-role-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-assign-task-to-role-proc.adoc @@ -12,7 +12,7 @@ image:cases/node_task_panel.png[] .Procedure . Open the *Activities* menu in the designer palette and drag the user or service task that you want to add to your case definition onto the process designer canvas. -. With the task node selected, click image:getting-started/diagram_properties.png[] to open the *Properties* panel on the right side of the designer. +. With the task node selected, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel on the right side of the designer. . Expand *Implementation/Execution*, click *Add* below the *Actors* property and either select or type the name of the role to which the task will be assigned. You can use the *Groups* property in the same way for group assignments. + For example, in the *IT_Orders* sample project, the `Manager approval` user task is assigned to the `manager` role: diff --git a/doc-content/enterprise-only/cases/case-management-create-sub-proc.adoc b/doc-content/enterprise-only/cases/case-management-create-sub-proc.adoc index b8f7a42319..9be0a91d66 100644 --- a/doc-content/enterprise-only/cases/case-management-create-sub-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-create-sub-proc.adoc @@ -15,22 +15,95 @@ Create the `Place order` sub-process, which is a separate business process that * *Package*: Select `com.myspace.it_orders_new` . Click *Ok*. The diagram editor opens. . Click an empty space in the canvas, and in the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[] in the *Process Variables* section and enter the following: +. Scroll down, expand *Process Data* and click image:getting-started/btn_plus.png[the plus sign icon] in the *Process Variables* section, and enter the following values under *Process Variables*: + -image::cases/proc-vars.png[] +.Process variables +[cols="1,2", options="header"] +|=== + +|Name +|Data Type + +|CaseID +|String + +|Requestor +|String + +|_hwSpec +|org.jbm.doc + +|ordered_ +|Boolean + +|info_ +|String + +|caseFile_hwSpec +|org.jbm.doc + +|caseFile-ordered +|Boolean + +|caseFile-orderinf +|String +|=== ++ +.Completed process variables +image::cases/proc-vars.png[screen capture of the process variables list] . Click *Save*. . Drag a start event onto the canvas and create an outgoing connection from the start event to a task and convert the new task to a user task. + -image::cases/start-event.png[] +image::cases/start-event.png[screen capture of Start Events menu] + -image::cases/new_task.png[] +image::cases/new_task.png[screen capture of Create Task icon] + -image::cases/user-task.png[] +image::cases/user-task.png[screen capture of Convert into User icon] . Click the user task and in the *Properties* panel, input `Place order` in the *Name* field. . Expand *Implementation/Execution*, click *Add* below the *Groups* menu, click *Select* -> *New*, and input `supplier`. -. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +. Click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following data inputs and outputs in the *Place order Data I/O* dialog box: ++ +.Data inputs and assignements +[cols="1,2,3", options="header"] +|=== + +|Name +|Data Type +|Source + +|_hwSpec +|org.jbpm.document +|caseFile_hwSpec + +|orderNumber +|String +|CaseId + +|Requestor +|String +|Requestor + +|=== + -image::cases/place-order-io1.png[] +.Data outputs and assignements +[cols="1,2,3", options="header"] +|=== + +|Name +|Data Type +|Target + +|ordered_ +|Boolean +|caseFile_ordered + +|info_ +|String +|CaseFile_orderInfo + +|=== ++ +image::cases/place-order-io1.png[screen capture of the Place order Data I/0 dialog] + For the first input assignment, select *Custom* for the *Data Type* and input `org.jbpm.document.Document`. @@ -38,11 +111,9 @@ For the first input assignment, select *Custom* for the *Data Type* and input `o . Select the *Skippable* check box and enter the following text in the *Description* field: + `Approved order #{CaseId} to be placed` -+ -image::cases/skip-description.png[] . Create an outgoing connection from the *Place order* user task and connect it to an end event. + -image::cases/create-end-event.png[] +image::cases/create-end-event.png[screen capture of the Place order user task] + -image::cases/sub-proc.png[] +image::cases/sub-proc.png[screen capture of the end event added to the Place order user task] . Click *Save* to confirm your changes. diff --git a/doc-content/enterprise-only/cases/case-management-creating-a-case-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-a-case-proc.adoc index f848227478..6b509931ac 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-a-case-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-a-case-proc.adoc @@ -6,18 +6,9 @@ Create a new `IT_Orders` project in {CENTRAL} to gain an understanding of all of .Procedure . Log in to {CENTRAL} and go to *Menu* -> *Design* -> *Projects*. + -{CENTRAL} provides a default space called *MySpace*, as shown in the following image. You can use the default space to create and test example projects. -+ -.Default spaces -image::getting-started/spaces-teams-bc.png[] +{CENTRAL} provides a default space called *MySpace*. You can use the default space to create and test example projects. . Click the *Add Project* drop-down arrow and select the *Case project* option: -+ -.Case project -image::cases/select-case-proj.png[] . In the *Add Project* window, enter `IT_Orders_New` in the *Name* field and enter a project *Description*. -+ -.Add Project window -image::getting-started/addproject-case.png[] . Click *Add* to add the project. + diff --git a/doc-content/enterprise-only/cases/case-management-creating-delivered-milestone-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-delivered-milestone-proc.adoc index 28c3aa45bb..46b7737f83 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-delivered-milestone-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-delivered-milestone-proc.adoc @@ -7,7 +7,7 @@ The condition for this milestone is that a case file variable named `delivered` . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Milestone 3: Delivered to customer` in the *Name* field. . Expand *Implementation/Execution* and ensure that *AdHoc Autostart* is not selected. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/milestone3IO.png[Delivered to customer I/O values] + @@ -23,7 +23,7 @@ Click the *Source* column drop-down, select *Constant*, and input `org.kie.api.r .. Select the *Skippable* check box and enter the following text in the in the *Description* field: + `Satisfaction survey for order #{CaseId}` -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. Click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/surveyIO.png[survey I/O values] + diff --git a/doc-content/enterprise-only/cases/case-management-creating-manager-approval-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-manager-approval-proc.adoc index 4da71d5066..a1e6fa9a7a 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-manager-approval-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-manager-approval-proc.adoc @@ -13,7 +13,7 @@ The manager approval process determines whether or not the order will be placed .. Select the *Skippable* check box and enter the following text in the *Description* field: + `Prepare hardware specification for #{initiator} (order number #{CaseId})` -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. Click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/hardware-spec-data.png[Prepare hardware I/O values] @@ -24,7 +24,7 @@ image::cases/hardware-spec-data.png[Prepare hardware I/O values] .. Click the user task and in the *Properties* panel input `Manager approval` in the *Name* field. .. Expand *Implementation/Execution*, click *Add* below the *Actors* menu, click *Select* -> *New*, and input `manager`. .. Input `ManagerApproval` in the *Task Name* field. -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. Click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/manager-approval-data.png[Manager approval I/O values] @@ -53,7 +53,7 @@ image::cases/connect-sub.png[Creating a Data-based Exclusive (XOR) gateway to su .. Click the new sub task and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. .. Input `Place order` in the *Name* field. -.. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/place-order-io.png[Place order I/O values] @@ -73,7 +73,7 @@ image::cases/second-task.png[Align new task] .. Input `Order rejected` in the *Name* field. .. Expand *Implementation/Execution* and input `OrderRejected` in the *Task Name* field. .. Click *Add* below the *Actors* menu, click *Select* -> *New*, and input `owner`. -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. Click image:getting-started/diagram_properties.png[rgw properties icon] in the *Assignments* field and add the following: + image::cases/order-rejected-io.png[Order rejected I/O values] diff --git a/doc-content/enterprise-only/cases/case-management-creating-manager-decision-milestone-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-manager-decision-milestone-proc.adoc index b6e480957f..78992dc28e 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-manager-decision-milestone-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-manager-decision-milestone-proc.adoc @@ -4,10 +4,10 @@ This milestone is reached when the `managerDecision` variable has been given a r .Procedure . In the process designer, expand *Milestone* in the *Object Library* and drag a new milestone onto the canvas below the *HardwareSpecReady* milestone. -. Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. +. Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[the Properties icon] icon in the upper-right corner. . Input `Manager decision` in the *Name* field. . Expand *Implementation/Execution* and select *AdHoc Autostart*. -. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/manager-dec-io.png[ManagerDecision I/O values] + diff --git a/doc-content/enterprise-only/cases/case-management-creating-order-placed-milestone-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-order-placed-milestone-proc.adoc index f991226ace..b3372075b4 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-order-placed-milestone-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-order-placed-milestone-proc.adoc @@ -7,7 +7,7 @@ This milestone is reached when the `ordered` variable, which is part of the *Pla . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Milestone 1: Order placed` in the *Name* field. . Expand *Implementation/Execution* and select *AdHoc Autostart*. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/milestone-evaluation-condition.png[Milestone evaluation condition configuration] + diff --git a/doc-content/enterprise-only/cases/case-management-creating-order-shipped-milestone-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-order-shipped-milestone-proc.adoc index 6191c72e73..9b3218e59a 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-order-shipped-milestone-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-order-shipped-milestone-proc.adoc @@ -7,7 +7,7 @@ The condition for this milestone is that a case file variable named `shipped` is . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Milestone 2: Order shipped` in the *Name* field. . Expand *Implementation/Execution* and ensure that *AdHoc Autostart* is not selected. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/ordershippedIO.png[Order shipped ready I/O values] + diff --git a/doc-content/enterprise-only/cases/case-management-creating-roles-proc.adoc b/doc-content/enterprise-only/cases/case-management-creating-roles-proc.adoc index 84028bc4e8..93b8964263 100644 --- a/doc-content/enterprise-only/cases/case-management-creating-roles-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-creating-roles-proc.adoc @@ -9,7 +9,7 @@ Case instances include the individuals that are actually handling the case work. * The case definition asset is open in the process designer. .Procedure -. To define the roles involved in the case, click on an empty space in the editor's canvas, and click image:getting-started/diagram_properties.png[] to open the *Properties* menu. +. To define the roles involved in the case, click on an empty space in the editor's canvas, and click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* menu. . Expand *Case Management* to add a case role. + The case role requires a name for the role and a case cardinality. Case cardinality is the number of actors that are assigned to the role in any case instance. For example, the *IT_Orders* sample case management project includes the following roles: diff --git a/doc-content/enterprise-only/cases/case-management-deploy-test-proc.adoc b/doc-content/enterprise-only/cases/case-management-deploy-test-proc.adoc index a33b47f303..bb0d3956e6 100644 --- a/doc-content/enterprise-only/cases/case-management-deploy-test-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-deploy-test-proc.adoc @@ -15,7 +15,4 @@ After you create and define all components of the new `IT_Orders_New` case proje . Click *Deploy*. . Go to *Menu* -> *Manage* -> *Process Definitions* -> *Manage Process Instances* -> *New Process Instance*. . Go to *Menu* -> *Deploy* and click *Execution Servers* and verify that a new container is deployed and started. -+ -image::cases/new-container.png[] - . Use the Case Management Showcase application to start a new case instance. For instructions about using the Showcase application, see {URL_DEVELOPING_PROCESS_SERVICES}#assembly-showcase-application[_{SHOWCASE_APPLICATION_CASE_MANAGEMENT}_]. diff --git a/doc-content/enterprise-only/cases/case-management-designing-IT-hardware-proc.adoc b/doc-content/enterprise-only/cases/case-management-designing-IT-hardware-proc.adoc index 838a149100..07baf536ff 100644 --- a/doc-content/enterprise-only/cases/case-management-designing-IT-hardware-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-designing-IT-hardware-proc.adoc @@ -19,27 +19,10 @@ image::cases/itorders-orderhardware-process.png[IT Orders case design] + * *Case Definition*: Input `orderhardware`. This is usually the subject of the case or project that is being case managed. * *Package*: Select *com.myspace.it_orders_new* to specify the location that the case file is created in. -//* `Case ID prefix (optional)`: A configurable prefix that enables you to easily distinguish different types of cases. The prefix is followed by a generated ID in the format `ID-XXXXXXXXXX`, where `XXXXXXXXXX` is a generated number that provides a unique ID for the case instance. If a prefix is not provided, the default prefix is `CASE` and generates instances with the following identifiers: -//+ -//`CASE-0000000001` -//+ -//`CASE-0000000002` -//+ -//`CASE-0000000003` -//+ -//If a prefix is set to something else, such as `IT` for example, the following identifiers are generated: -//+ -//`IT-0000000001` -//+ -//`IT-0000000002` -//+ -//`IT-0000000003` - -+ . Click *Ok* to open the process designer. . Define values for the case file variables that are accessible to the sub-processes, subcases, and business rules used in the case. .. In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[] in the *Case File Variables* section, and enter the following: +.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[the plus sign icon] in the *Case File Variables* section, and enter the following: + .orderhardware case file variables image::cases/case-file-vars.png[Case file variables] @@ -56,7 +39,7 @@ The following case file variables are custom data types: . Click *Save*. . Define the roles involved in the case. .. In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[] in the *Case Roles* section, and enter the following: +.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[the plus sign icon] in the *Case Roles* section, and enter the following: + .orderhardware case roles image::cases/case_roles-2.png[Case roles] diff --git a/doc-content/enterprise-only/cases/case-management-milestone-triggering-proc.adoc b/doc-content/enterprise-only/cases/case-management-milestone-triggering-proc.adoc index 2ff230dc5b..93ec64fbad 100644 --- a/doc-content/enterprise-only/cases/case-management-milestone-triggering-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-milestone-triggering-proc.adoc @@ -14,7 +14,7 @@ Case milestones can be configured to start automatically when a case instance st image::cases/milestone.png[Milestone] + -. With the milestone selected, click image:getting-started/diagram_properties.png[] to open the *Properties* panel on the right side of the designer. +. With the milestone selected, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel on the right side of the designer. . Expand *Data Assignments* to add a completion condition. Milestones include a `Condition` parameter by default. . To define the completion condition for the milestone, select `Constant` from the *Source* list. The condition must be provided using the Drools syntax. . Expand *Implementation/Execution* to configure the `AdHoc Autostart` property. diff --git a/doc-content/enterprise-only/cases/case-management-stage-activation-and-completion-conditions-proc.adoc b/doc-content/enterprise-only/cases/case-management-stage-activation-and-completion-conditions-proc.adoc index eed73e5970..8d22262c65 100644 --- a/doc-content/enterprise-only/cases/case-management-stage-activation-and-completion-conditions-proc.adoc +++ b/doc-content/enterprise-only/cases/case-management-stage-activation-and-completion-conditions-proc.adoc @@ -15,7 +15,7 @@ Activation conditions can also be configured using a free-form Drools rule to co * You have added an ad hoc sub-process to the case definition that is to be used as a stage. .Procedure -. With the stage selected, click image:getting-started/diagram_properties.png[] to open the *Properties* panel on the right side of the designer. +. With the stage selected, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel on the right side of the designer. . Expand *Implementation/Execution* and in the `AdHocActivationCondition` property editor define an activation condition for the start node. For example, set `autostart: true` to make the stage automatically activated when a new case instance is started. . The `AdHocCompletionCondition` is set to `autocomplete` by default. To change this, input a completion condition using a free-form Drools expression. For example, set `org.kie.api.runtime.process.CaseData(data.get("ordered") == true)` to activate the second stage in the example shown previously. diff --git a/doc-content/enterprise-only/cases/order-service-data-object-proc.adoc b/doc-content/enterprise-only/cases/order-service-data-object-proc.adoc index efc128f666..c1bdb43acd 100644 --- a/doc-content/enterprise-only/cases/order-service-data-object-proc.adoc +++ b/doc-content/enterprise-only/cases/order-service-data-object-proc.adoc @@ -12,6 +12,6 @@ The `ITOrderService` data object specifies the data type that will be used to de * Data Object: `ITOrderService` * Package: `com.myspace.it_orders_new` . Click *Ok*. -. Click image:cases/plus-sign.png[] next to the *Package* drop-down menu to specify a new package for the data object. +. Click image:cases/plus-sign.png[the plus sign icon] next to the *Package* drop-down menu to specify a new package for the data object. . Input `org.jbpm.demo.it_orders.services` and click *Add*. . Click *Save*, and then click *Yes, Move* to confirm your changes. diff --git a/doc-content/enterprise-only/cases/survey-data-object-proc.adoc b/doc-content/enterprise-only/cases/survey-data-object-proc.adoc index 54845c5325..ebd1237a07 100644 --- a/doc-content/enterprise-only/cases/survey-data-object-proc.adoc +++ b/doc-content/enterprise-only/cases/survey-data-object-proc.adoc @@ -36,4 +36,4 @@ The `Survey` data object contains data fields, such as *deliveredOnTime* and *mi + .Survey data object details -image::cases/survey-do.png[] +image::cases/survey-do.png[screen capture of the survey data objects dialog] diff --git a/doc-content/enterprise-only/getting-started/business-process-con.adoc b/doc-content/enterprise-only/getting-started/business-process-con.adoc index 9067a0ef9a..b2d22e0854 100644 --- a/doc-content/enterprise-only/getting-started/business-process-con.adoc +++ b/doc-content/enterprise-only/getting-started/business-process-con.adoc @@ -5,4 +5,4 @@ A business process is a diagram that describes the order in which a series of st The sample *Mortgage_Process* contains the following predefined *MortgageApprovalProcess* business process. -image:getting-started/sampleBP.png[] +image:getting-started/sampleBP.png[screen capture of the mortgageApprovalProcess business process] diff --git a/doc-content/enterprise-only/getting-started/business-process-proc.adoc b/doc-content/enterprise-only/getting-started/business-process-proc.adoc index 6b6165637a..2604ef6d6f 100644 --- a/doc-content/enterprise-only/getting-started/business-process-proc.adoc +++ b/doc-content/enterprise-only/getting-started/business-process-proc.adoc @@ -15,7 +15,7 @@ The *Package* specifies the location inside the existing project where the asset . Click *Ok*. The diagram editor opens. . In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[] in the *Process Variables* section. +. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[the plus sign icon] in the *Process Variables* section. . Enter the following values: + * *Name*: `application` @@ -152,7 +152,7 @@ image::getting-started/validconnection.png[] .Mortgage Calculation Data I/O assignments image::getting-started/mortgage-calc-assignments.png[screen capture of the Mortgage Calculation Data I/O assignments] -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: * *Name*: `inlimit` * *Data Type*: `Boolean` @@ -202,7 +202,7 @@ image::getting-started/new-task.png[] . Click the connection and input `Not in Limit` in the *Name* field of the *Properties* panel. . Expand *Implementation/Execution* and select *Condition* in the *Condition Expression* section. . Select *inlimit* from the *Process Variable* drop-down menu and select *Is false* from the *Condition* drop-down menu. -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: + * *Name*: `incdownpayment` * *Data Type*: `Boolean` diff --git a/doc-content/enterprise-only/getting-started/business-rules-proc.adoc b/doc-content/enterprise-only/getting-started/business-rules-proc.adoc index 5de70d8b25..c062792373 100644 --- a/doc-content/enterprise-only/getting-started/business-rules-proc.adoc +++ b/doc-content/enterprise-only/getting-started/business-rules-proc.adoc @@ -11,7 +11,7 @@ Review the *WHEN* and *THEN* rules so that you understand how the conditions are . From the asset list, click the right arrow to view the second page of the asset list and click the *Validate Down Payment* guided rule. . Review the *Validate Down Payment* guided rule's *WHEN* and *THEN* conditions and values. + -image::getting-started/validate-rules.png[] +image::getting-started/validate-rules.png[screen caputure of the Validate Down Payment.drl Guided Rules dialog] == Viewing the *RetractValidationErr* guided rule Review the *WHEN* and *THEN* rules so that you understand how the conditions are set and used later when you run the process. diff --git a/doc-content/enterprise-only/getting-started/decision-tables-proc.adoc b/doc-content/enterprise-only/getting-started/decision-tables-proc.adoc index 24d94cc8fc..32880755b1 100644 --- a/doc-content/enterprise-only/getting-started/decision-tables-proc.adoc +++ b/doc-content/enterprise-only/getting-started/decision-tables-proc.adoc @@ -82,4 +82,4 @@ The goal of this chapter is to introduce you to the *MortgageDecisionTable* deci . In {CENTRAL}, go to *Menu* -> *Design* -> *Projects* -> *Mortgage_Process*. . Scroll down and click the *MortgageDecisionTable* Guided Decision Tables asset. + -image:getting-started/loans-guided-dt.png[] +image:getting-started/loans-guided-dt.png[screen capture of the MortgageDecisionTable Guided Decision Tables asset] diff --git a/doc-content/enterprise-only/getting-started/executing-proc.adoc b/doc-content/enterprise-only/getting-started/executing-proc.adoc index eb6cfc0ddc..0702d3a8d4 100644 --- a/doc-content/enterprise-only/getting-started/executing-proc.adoc +++ b/doc-content/enterprise-only/getting-started/executing-proc.adoc @@ -28,7 +28,7 @@ Now that you have deployed the project, you can execute the project's defined fu . Click *Submit* to start a new process instance. After starting the process instance, the *Instance Details* view opens. . Click the *Diagram* tab to view the process flow within the process diagram. The state of the process is highlighted as it moves through each task. + -image::project-data/diagram-progress.png[] +image::project-data/diagram-progress.png[screen capture of the process flow within the process diagram] . Log out of {Central} and log back in as `Katy`. . Click *Menu* -> *Track* -> *Task Inbox*. This takes you to the *Qualify* form. diff --git a/doc-content/enterprise-only/processes/asynchronous-signal-end-events-proc.adoc b/doc-content/enterprise-only/processes/asynchronous-signal-end-events-proc.adoc index 72d4903d0d..036ac7bab1 100644 --- a/doc-content/enterprise-only/processes/asynchronous-signal-end-events-proc.adoc +++ b/doc-content/enterprise-only/processes/asynchronous-signal-end-events-proc.adoc @@ -15,7 +15,7 @@ You can configure an asynchronous signal for end events in {CENTRAL}. . Open a business process asset. . In the process designer canvas, drag and drop the *End Signal* from the left toolbar. -. In the upper-right corner, click image:getting-started/diagram_properties.png[] to open the *Properties* panel. +. In the upper-right corner, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel. . Expand *Data Assignments*. . Click the box under the *Assignments* sub-section. The *Task Data I/O* dialog box opens. . Click *Add* next to *Data Inputs and Assignments*. diff --git a/doc-content/enterprise-only/processes/asynchronous-signal-intermediate-events-proc.adoc b/doc-content/enterprise-only/processes/asynchronous-signal-intermediate-events-proc.adoc index 5c65afb513..877fc764c2 100644 --- a/doc-content/enterprise-only/processes/asynchronous-signal-intermediate-events-proc.adoc +++ b/doc-content/enterprise-only/processes/asynchronous-signal-intermediate-events-proc.adoc @@ -15,7 +15,7 @@ You can configure an asynchronous signal for intermediate events in {CENTRAL}. . Open a business process asset. . In the process designer canvas, drag and drop the *Intermediate Signal* from the left toolbar. -. In the upper-right corner, click image:getting-started/diagram_properties.png[] to open the *Properties* panel. +. In the upper-right corner, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel. . Expand *Data Assignments*. . Click the box under the *Assignments* sub-section. The *Task Data I/O* dialog box opens. . Click *Add* next to *Data Inputs and Assignments*. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/bpmn-subprocesses-ref.adoc b/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/bpmn-subprocesses-ref.adoc index cf58c6dd63..fdbc25826d 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/bpmn-subprocesses-ref.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/bpmn-subprocesses-ref.adoc @@ -28,7 +28,7 @@ An embedded sub-process encapsulates a part of the process. It must contain a st An ad hoc sub-process or process contains a number of embedded inner activities and is intended to be executed with a more flexible ordering compared to the typical process flow. Unlike regular processes, an ad hoc sub-process does not contain a complete, structured BPMN2 diagram description, for example, from start event to end event. Instead, the ad hoc sub-process contains only activities, sequence flows, gateways, and intermediate events. An ad hoc sub-process can also contain data objects and data associations. The activities within the ad hoc sub-processes are not required to have incoming and outgoing sequence flows. However, you can specify sequence flows between some of the contained activities. When used, sequence flows provide the same ordering constraints as in a regular process. To have any meaning, intermediate events must have outgoing sequence flows and they can be triggered multiple times while the ad hoc sub-process is active. .Reusable sub-process -Reusable sub-processes appear collapsed within the parent process. To configure a reusable sub-process, select the reusable sub-process, click image:getting-started/diagram_properties.png[], and expand *Implementation/Execution*. Set the following properties: +Reusable sub-processes appear collapsed within the parent process. To configure a reusable sub-process, select the reusable sub-process, click image:getting-started/diagram_properties.png[the Properties icon], and expand *Implementation/Execution*. Set the following properties: * *Called Element*: The ID of the sub-process that the activity calls and instantiates. * *Independent*: If selected, the sub-process is started as an independent process. If not selected, the active sub-process is canceled when the parent process is terminated. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/create-doc-var-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/create-doc-var-proc.adoc index 998c2a6ee2..3ba45a3f8c 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/create-doc-var-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/create-doc-var-proc.adoc @@ -10,7 +10,7 @@ After you set a document marshalling strategy, create a document variable in the .Procedure . In {CENTRAL}, go to *Menu* -> *Design* -> *Projects*. . Click the project name to open the asset view and click the business process name. -. Click the canvas and click image:getting-started/diagram_properties.png[] on the right side of the window to open the *Properties* panel. +. Click the canvas and click image:getting-started/diagram_properties.png[the Properties icon] on the right side of the window to open the *Properties* panel. . Expand *Process Data* and click image:getting-started/6176.png[] and enter the following values: + * *Name*: `document` diff --git a/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/map-task-vars-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/map-task-vars-proc.adoc index f78ea1d863..f9895e5f6d 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/map-task-vars-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/BPMN2/map-task-vars-proc.adoc @@ -10,7 +10,7 @@ If you want to view or modify the attachments inside of task forms, create assig .Procedure . In {CENTRAL}, go to *Menu* -> *Design* -> *Projects*. . Click the project name to open the asset view and click the business process name. -. Click a user task and click image:getting-started/diagram_properties.png[] on the right side of the window to open the *Properties* panel. +. Click a user task and click image:getting-started/diagram_properties.png[the Properties icon] on the right side of the window to open the *Properties* panel. . Expand *Implementation/Execution* and next to *Assignments*, click image:getting-started/btn_assign.png[] to open the *Data I/O* window. . Next to *Data Inputs and Assignments*, click *Add* and enter the following values: + diff --git a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-assign-task-to-role-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-assign-task-to-role-proc.adoc index eb17a362d2..c7eda84054 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-assign-task-to-role-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-assign-task-to-role-proc.adoc @@ -12,7 +12,7 @@ image:cases/node_task_panel.png[] .Procedure . Open the *Activities* menu in the designer palette and drag the user or service task that you want to add to your case definition onto the process designer canvas. -. With the task node selected, click image:getting-started/diagram_properties.png[] to open the *Properties* panel on the right side of the designer. +. With the task node selected, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel on the right side of the designer. . Expand *Implementation/Execution*, click *Add* below the *Actors* property and either select or type the name of the role to which the task will be assigned. You can use the *Groups* property in the same way for group assignments. + For example, in the *IT_Orders* sample project, the `Manager approval` user task is assigned to the `manager` role: diff --git a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-creating-roles-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-creating-roles-proc.adoc index 84028bc4e8..93b8964263 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-creating-roles-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-creating-roles-proc.adoc @@ -9,7 +9,7 @@ Case instances include the individuals that are actually handling the case work. * The case definition asset is open in the process designer. .Procedure -. To define the roles involved in the case, click on an empty space in the editor's canvas, and click image:getting-started/diagram_properties.png[] to open the *Properties* menu. +. To define the roles involved in the case, click on an empty space in the editor's canvas, and click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* menu. . Expand *Case Management* to add a case role. + The case role requires a name for the role and a case cardinality. Case cardinality is the number of actors that are assigned to the role in any case instance. For example, the *IT_Orders* sample case management project includes the following roles: diff --git a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-milestone-triggering-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-milestone-triggering-proc.adoc index 2ff230dc5b..93ec64fbad 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-milestone-triggering-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-milestone-triggering-proc.adoc @@ -14,7 +14,7 @@ Case milestones can be configured to start automatically when a case instance st image::cases/milestone.png[Milestone] + -. With the milestone selected, click image:getting-started/diagram_properties.png[] to open the *Properties* panel on the right side of the designer. +. With the milestone selected, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel on the right side of the designer. . Expand *Data Assignments* to add a completion condition. Milestones include a `Condition` parameter by default. . To define the completion condition for the milestone, select `Constant` from the *Source* list. The condition must be provided using the Drools syntax. . Expand *Implementation/Execution* to configure the `AdHoc Autostart` property. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-stage-activation-and-completion-conditions-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-stage-activation-and-completion-conditions-proc.adoc index eed73e5970..8d22262c65 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-stage-activation-and-completion-conditions-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/DesignBuildCases/case-management-stage-activation-and-completion-conditions-proc.adoc @@ -15,7 +15,7 @@ Activation conditions can also be configured using a free-form Drools rule to co * You have added an ad hoc sub-process to the case definition that is to be used as a stage. .Procedure -. With the stage selected, click image:getting-started/diagram_properties.png[] to open the *Properties* panel on the right side of the designer. +. With the stage selected, click image:getting-started/diagram_properties.png[the Properties icon] to open the *Properties* panel on the right side of the designer. . Expand *Implementation/Execution* and in the `AdHocActivationCondition` property editor define an activation condition for the start node. For example, set `autostart: true` to make the stage automatically activated when a new case instance is started. . The `AdHocCompletionCondition` is set to `autocomplete` by default. To change this, input a completion condition using a free-form Drools expression. For example, set `org.kie.api.runtime.process.CaseData(data.get("ordered") == true)` to activate the second stage in the example shown previously. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-con.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-con.adoc index 9067a0ef9a..b2d22e0854 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-con.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-con.adoc @@ -5,4 +5,4 @@ A business process is a diagram that describes the order in which a series of st The sample *Mortgage_Process* contains the following predefined *MortgageApprovalProcess* business process. -image:getting-started/sampleBP.png[] +image:getting-started/sampleBP.png[screen capture of the mortgageApprovalProcess business process] diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-proc.adoc index 3cd096902b..1eb99133bc 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-process-proc.adoc @@ -15,7 +15,7 @@ The *Package* specifies the location inside the existing project where the asset . Click *Ok*. The diagram editor opens. . In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[] in the *Process Variables* section. +. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[the plus sign icon] in the *Process Variables* section. . Enter the following values: + * *Name*: `application` @@ -155,7 +155,7 @@ image::getting-started/validconnection.png[] image::getting-started/mortgage-calc-assignments.png[screen capture of the Mortgage Calculation Data I/O assignments] . Click *OK* in the *Mortgage Calculation Data I/O* window. -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: * *Name*: `inlimit` * *Data Type*: `Boolean` @@ -207,7 +207,7 @@ image::getting-started/new-task.png[] . Click the connection and input `Not in Limit` in the *Name* field of the *Properties* panel. . Expand *Implementation/Execution* and select *Condition* in the *Condition Expression* section. . Select *inlimit* from the *Process Variable* drop-down menu and select *Is false* from the *Condition* drop-down menu. -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: + * *Name*: `incdownpayment` * *Data Type*: `Boolean` diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-rules-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-rules-proc.adoc index 5de70d8b25..c062792373 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-rules-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/business-rules-proc.adoc @@ -11,7 +11,7 @@ Review the *WHEN* and *THEN* rules so that you understand how the conditions are . From the asset list, click the right arrow to view the second page of the asset list and click the *Validate Down Payment* guided rule. . Review the *Validate Down Payment* guided rule's *WHEN* and *THEN* conditions and values. + -image::getting-started/validate-rules.png[] +image::getting-started/validate-rules.png[screen caputure of the Validate Down Payment.drl Guided Rules dialog] == Viewing the *RetractValidationErr* guided rule Review the *WHEN* and *THEN* rules so that you understand how the conditions are set and used later when you run the process. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/executing-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/executing-proc.adoc index eb6cfc0ddc..0702d3a8d4 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/executing-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedBusProc/executing-proc.adoc @@ -28,7 +28,7 @@ Now that you have deployed the project, you can execute the project's defined fu . Click *Submit* to start a new process instance. After starting the process instance, the *Instance Details* view opens. . Click the *Diagram* tab to view the process flow within the process diagram. The state of the process is highlighted as it moves through each task. + -image::project-data/diagram-progress.png[] +image::project-data/diagram-progress.png[screen capture of the process flow within the process diagram] . Log out of {Central} and log back in as `Katy`. . Click *Menu* -> *Track* -> *Task Inbox*. This takes you to the *Qualify* form. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-create-sub-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-create-sub-proc.adoc index e713111210..c59f178b60 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-create-sub-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-create-sub-proc.adoc @@ -15,22 +15,96 @@ Create the `Place order` sub-process, which is a separate business process that * *Package*: Select `com.myspace.it_orders_new` . Click *Ok*. The diagram editor opens. . Click an empty space in the canvas, and in the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[] in the *Process Variables* section and enter the following: +. Scroll down, expand *Process Data*, click image:getting-started/btn_plus.png[the plus sign icon] in the *Process Variables* section, and enter the following values under *Process Variables*: + -image::cases/proc-vars.png[] +.Process variables +[cols="1,2", options="header"] +|=== + +|Name +|Data Type + +|CaseID +|String + +|Requestor +|String + +|_hwSpec +|org.jbm.doc + +|ordered_ +|Boolean + +|info_ +|String + +|caseFile_hwSpec +|org.jbm.doc + +|caseFile-ordered +|Boolean + +|caseFile-orderinf +|String +|=== ++ +.Completed process variables +image::cases/proc-vars.png[screen capture of the process variables list] + . Click *Save*. . Drag a start event onto the canvas and create an outgoing connection from the start event to a task and convert the new task to a user task. + -image::cases/start-event.png[] +[screen capture of Start Events menu] + -image::cases/new_task.png[] +image::cases/new_task.png[screen capture of Create Task icon] + -image::cases/user-task.png[] +image::cases/user-task.png[screen capture of Convert into User icon] . Click the user task and in the *Properties* panel, input `Place order` in the *Name* field. . Expand *Implementation/Execution*, click *Add* below the *Groups* menu, click *Select* -> *New*, and input `supplier`. -. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +. click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following data inputs and outputs in the *Place order Data I/O* dialog box: + -image::cases/place-order-io1.png[] +.Data inputs and assignements +[cols="1,2,3", options="header"] +|=== + +|Name +|Data Type +|Source + +|_hwSpec +|org.jbpm.document +|caseFile_hwSpec + +|orderNumber +|String +|CaseId + +|Requestor +|String +|Requestor + +|=== ++ +.Data outputs and assignements +[cols="1,2,3", options="header"] +|=== + +|Name +|Data Type +|Target + +|ordered_ +|Boolean +|caseFile_ordered + +|info_ +|String +|CaseFile_orderInfo + +|=== ++ +image::cases/place-order-io1.png[screen capture of the Place order Data I/0 dialog] + For the first input assignment, select *Custom* for the *Data Type* and input `org.jbpm.document.Document`. @@ -38,15 +112,13 @@ For the first input assignment, select *Custom* for the *Data Type* and input `o . Select the *Skippable* check box and enter the following text in the *Description* field: + `Approved order #{CaseId} to be placed` -+ -image::cases/skip-description.png[] . Create an outgoing connection from the *Place order* user task and connect it to an end event. + -image::cases/create-end-event.png[] +image::cases/create-end-event.png[screen capture of the Place order user task] + -image::cases/sub-proc.png[] +image::cases/sub-proc.png[screen capture of the end event added to the Place order user task] . Click *Save* to confirm your changes. You can open the sub-process in a new editor in {CENTRAL} by clicking the *Place order* task in the main process and then clicking the *Open Sub-process* task icon. -image::cases/open-sub-proc.png[] +image::cases/open-sub-proc.png[screen capture of the Open Sub-process icon] diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-a-case-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-a-case-proc.adoc index f848227478..5ca6c14832 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-a-case-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-a-case-proc.adoc @@ -6,19 +6,9 @@ Create a new `IT_Orders` project in {CENTRAL} to gain an understanding of all of .Procedure . Log in to {CENTRAL} and go to *Menu* -> *Design* -> *Projects*. + -{CENTRAL} provides a default space called *MySpace*, as shown in the following image. You can use the default space to create and test example projects. -+ -.Default spaces -image::getting-started/spaces-teams-bc.png[] +{CENTRAL} provides a default space called *MySpace*. You can use the default space to create and test example projects. . Click the *Add Project* drop-down arrow and select the *Case project* option: -+ -.Case project -image::cases/select-case-proj.png[] . In the *Add Project* window, enter `IT_Orders_New` in the *Name* field and enter a project *Description*. -+ -.Add Project window -image::getting-started/addproject-case.png[] . Click *Add* to add the project. + - The *Assets* view of the project opens. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-delivered-milestone-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-delivered-milestone-proc.adoc index 587f8c7a20..6450d54d7c 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-delivered-milestone-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-delivered-milestone-proc.adoc @@ -7,7 +7,7 @@ The condition for this milestone is that a case file variable named `delivered` . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Milestone 3: Delivered to customer` in the *Name* field. . Expand *Implementation/Execution* and ensure that *AdHoc Autostart* is not selected. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/milestone3IO.png[Delivered to customer I/O values] + @@ -23,7 +23,7 @@ Click the *Source* column drop-down, select *Constant*, and input `org.kie.api.r .. Select the *Skippable* check box and enter the following text in the in the *Description* field: + `Satisfaction survey for order #{CaseId}` -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/surveyIO.png[survey I/O values] + diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-hardware-spec-ready-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-hardware-spec-ready-proc.adoc index 1ea5ebcbf8..b05c06c078 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-hardware-spec-ready-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-hardware-spec-ready-proc.adoc @@ -7,7 +7,7 @@ Create a *HardwareSpecReady* milestone that is reached when the required hardwar . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Hardware spec ready` in the *Name* field. . Expand *Implementation/Execution* and select *AdHoc Autostart*. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/hardware-io.png[HardwareSpecReady I/O values] + diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-approval-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-approval-proc.adoc index 4dc8d07915..8fbaea0b69 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-approval-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-approval-proc.adoc @@ -13,7 +13,7 @@ The manager approval process determines whether or not the order will be placed .. Select the *Skippable* check box and enter the following text in the *Description* field: + `Prepare hardware specification for #{initiator} (order number #{CaseId})` -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/hardware-spec-data.png[Prepare hardware I/O values] @@ -24,7 +24,7 @@ image::cases/hardware-spec-data.png[Prepare hardware I/O values] .. Click the user task and in the *Properties* panel input `Manager approval` in the *Name* field. .. Expand *Implementation/Execution*, click *Add* below the *Actors* menu, click *Select* -> *New*, and input `manager`. .. Input `ManagerApproval` in the *Task Name* field. -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/manager-approval-data.png[Manager approval I/O values] @@ -53,7 +53,7 @@ image::cases/connect-sub.png[Creating a Data-based Exclusive (XOR) gateway to su .. Click the new sub task and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. .. Input `Place order` in the *Name* field. -.. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/place-order-io.png[Place order I/O values] @@ -74,7 +74,7 @@ image::cases/second-task.png[Align new task] .. Input `Order rejected` in the *Name* field. .. Expand *Implementation/Execution* and input `OrderRejected` in the *Task Name* field. .. Click *Add* below the *Actors* menu, click *Select* -> *New*, and input `owner`. -.. Click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +.. click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/order-rejected-io.png[Order rejected I/O values] diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-decision-milestone-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-decision-milestone-proc.adoc index c2c26228bb..32f581d3be 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-decision-milestone-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-manager-decision-milestone-proc.adoc @@ -7,7 +7,7 @@ This milestone is reached when the `managerDecision` variable has been given a r . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Manager decision` in the *Name* field. . Expand *Implementation/Execution* and select *AdHoc Autostart*. -. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[] in the *Assignments* field and add the following: +. Expand *Data Assignments* and click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field and add the following: + image::cases/manager-dec-io.png[ManagerDecision I/O values] + diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-placed-milestone-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-placed-milestone-proc.adoc index b12a00a153..02b7d9f9f9 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-placed-milestone-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-placed-milestone-proc.adoc @@ -7,7 +7,7 @@ This milestone is reached when the `ordered` variable, which is part of the *Pla . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Milestone 1: Order placed` in the *Name* field. . Expand *Implementation/Execution* and select *AdHoc Autostart*. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/milestone-evaluation-condition.png[Milestone evaluation condition configuration] + diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-shipped-milestone-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-shipped-milestone-proc.adoc index de4ce31f05..0ddbc5a186 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-shipped-milestone-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-creating-order-shipped-milestone-proc.adoc @@ -7,7 +7,7 @@ The condition for this milestone is that a case file variable named `shipped` is . Click the new milestone and click the *Properties* image:getting-started/diagram_properties.png[] icon in the upper-right corner. . Input `Milestone 2: Order shipped` in the *Name* field. . Expand *Implementation/Execution* and ensure that *AdHoc Autostart* is not selected. -. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[] in the *Assignments* field, and add the following: +. Expand *Data Assignments*, click image:getting-started/diagram_properties.png[the Properties icon] in the *Assignments* field, and add the following: + image::cases/ordershippedIO.png[Order shipped ready I/O values] + diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-deploy-test-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-deploy-test-proc.adoc index a33b47f303..bb0d3956e6 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-deploy-test-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-deploy-test-proc.adoc @@ -15,7 +15,4 @@ After you create and define all components of the new `IT_Orders_New` case proje . Click *Deploy*. . Go to *Menu* -> *Manage* -> *Process Definitions* -> *Manage Process Instances* -> *New Process Instance*. . Go to *Menu* -> *Deploy* and click *Execution Servers* and verify that a new container is deployed and started. -+ -image::cases/new-container.png[] - . Use the Case Management Showcase application to start a new case instance. For instructions about using the Showcase application, see {URL_DEVELOPING_PROCESS_SERVICES}#assembly-showcase-application[_{SHOWCASE_APPLICATION_CASE_MANAGEMENT}_]. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-designing-IT-hardware-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-designing-IT-hardware-proc.adoc index 838a149100..7d34d43de6 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-designing-IT-hardware-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/case-management-designing-IT-hardware-proc.adoc @@ -39,7 +39,7 @@ image::cases/itorders-orderhardware-process.png[IT Orders case design] . Click *Ok* to open the process designer. . Define values for the case file variables that are accessible to the sub-processes, subcases, and business rules used in the case. .. In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[] in the *Case File Variables* section, and enter the following: +.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[the plus sign icon] in the *Case File Variables* section, and enter the following: + .orderhardware case file variables image::cases/case-file-vars.png[Case file variables] @@ -56,7 +56,7 @@ The following case file variables are custom data types: . Click *Save*. . Define the roles involved in the case. .. In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[] in the *Case Roles* section, and enter the following: +.. Scroll down and expand *Case Management*, click image:getting-started/btn_plus.png[the plus sign icon] in the *Case Roles* section, and enter the following: + .orderhardware case roles image::cases/case_roles-2.png[Case roles] diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/order-service-data-object-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/order-service-data-object-proc.adoc index efc128f666..c1bdb43acd 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/order-service-data-object-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/order-service-data-object-proc.adoc @@ -12,6 +12,6 @@ The `ITOrderService` data object specifies the data type that will be used to de * Data Object: `ITOrderService` * Package: `com.myspace.it_orders_new` . Click *Ok*. -. Click image:cases/plus-sign.png[] next to the *Package* drop-down menu to specify a new package for the data object. +. Click image:cases/plus-sign.png[the plus sign icon] next to the *Package* drop-down menu to specify a new package for the data object. . Input `org.jbpm.demo.it_orders.services` and click *Add*. . Click *Save*, and then click *Yes, Move* to confirm your changes. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/survey-data-object-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/survey-data-object-proc.adoc index 54845c5325..ebd1237a07 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/survey-data-object-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedCaseManagement/survey-data-object-proc.adoc @@ -36,4 +36,4 @@ The `Survey` data object contains data fields, such as *deliveredOnTime* and *mi + .Survey data object details -image::cases/survey-do.png[] +image::cases/survey-do.png[screen capture of the survey data objects dialog] diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc index 9067a0ef9a..b2d22e0854 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-con.adoc @@ -5,4 +5,4 @@ A business process is a diagram that describes the order in which a series of st The sample *Mortgage_Process* contains the following predefined *MortgageApprovalProcess* business process. -image:getting-started/sampleBP.png[] +image:getting-started/sampleBP.png[screen capture of the mortgageApprovalProcess business process] diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc index 6b6165637a..2604ef6d6f 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-process-proc.adoc @@ -15,7 +15,7 @@ The *Package* specifies the location inside the existing project where the asset . Click *Ok*. The diagram editor opens. . In the upper-right corner, click the *Properties* image:getting-started/diagram_properties.png[] icon. -. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[] in the *Process Variables* section. +. Scroll down and expand *Process Data* and click image:getting-started/btn_plus.png[the plus sign icon] in the *Process Variables* section. . Enter the following values: + * *Name*: `application` @@ -152,7 +152,7 @@ image::getting-started/validconnection.png[] .Mortgage Calculation Data I/O assignments image::getting-started/mortgage-calc-assignments.png[screen capture of the Mortgage Calculation Data I/O assignments] -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: * *Name*: `inlimit` * *Data Type*: `Boolean` @@ -202,7 +202,7 @@ image::getting-started/new-task.png[] . Click the connection and input `Not in Limit` in the *Name* field of the *Properties* panel. . Expand *Implementation/Execution* and select *Condition* in the *Condition Expression* section. . Select *inlimit* from the *Process Variable* drop-down menu and select *Is false* from the *Condition* drop-down menu. -. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[] next to *Process Variables*. Enter the following values: +. Click an empty space on the canvas, scroll down, expand *Process Data*, and click image:getting-started/btn_plus.png[the plus sign icon] next to *Process Variables*. Enter the following values: + * *Name*: `incdownpayment` * *Data Type*: `Boolean` diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc index 5de70d8b25..c062792373 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/business-rules-proc.adoc @@ -11,7 +11,7 @@ Review the *WHEN* and *THEN* rules so that you understand how the conditions are . From the asset list, click the right arrow to view the second page of the asset list and click the *Validate Down Payment* guided rule. . Review the *Validate Down Payment* guided rule's *WHEN* and *THEN* conditions and values. + -image::getting-started/validate-rules.png[] +image::getting-started/validate-rules.png[screen caputure of the Validate Down Payment.drl Guided Rules dialog] == Viewing the *RetractValidationErr* guided rule Review the *WHEN* and *THEN* rules so that you understand how the conditions are set and used later when you run the process. diff --git a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc index eb6cfc0ddc..0702d3a8d4 100644 --- a/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc +++ b/doc-content/jbpm-docs/src/main/asciidoc/GettingStartedDecServices/executing-proc.adoc @@ -28,7 +28,7 @@ Now that you have deployed the project, you can execute the project's defined fu . Click *Submit* to start a new process instance. After starting the process instance, the *Instance Details* view opens. . Click the *Diagram* tab to view the process flow within the process diagram. The state of the process is highlighted as it moves through each task. + -image::project-data/diagram-progress.png[] +image::project-data/diagram-progress.png[screen capture of the process flow within the process diagram] . Log out of {Central} and log back in as `Katy`. . Click *Menu* -> *Track* -> *Task Inbox*. This takes you to the *Qualify* form.