pefernan commented on code in PR #1833:
URL:
https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1426824380
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that
drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration
including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the
`kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying
the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them
can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person
that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer
that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on
the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and
skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer
for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the
candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` )
matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a
`tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the
`tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags |
Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The
candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The
generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** |
Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** |
Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it
into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach
the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without
sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New
Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate
experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that
will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR
Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and
`offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will
prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary
Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and
deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the
**IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will
take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* &
*IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that
will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned
to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension:
https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages
(glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM
installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the
required services. This setup ensures that all services are connected with a
default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the
`startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a
```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script
for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that
will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the
following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
Review Comment:
Apparently that's a missing feature on `podman` prior `4.7`. I'll add a note
warning about this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
