process-business-rules-quarkus

Process with Business Rules

Description

A quickstart project that shows the use of business rules and processes

This example shows

• make use of DRL to define rules
• make use of business rules task in the process to evaluate rules

• Diagram Properties (top)

• Diagram Properties (bottom)

• Evaluate Person Business Rule (top)

• Evaluate Person Business Rule (bottom)

• Evaluate Person Business Rule (Assignments)

• Exclusive Gateway

• Exclusive Gateway For Adult Connector

• Exclusive Gateway For Children Connector

• Special Handling for Children (top)

• Special Handling for Children (middle)

• Special Handling for Children (bottom)

• Special Handling for Children (Assignments)

Build and run

Prerequisites

You will need:

• Java 11+ installed
• Environment variable JAVA_HOME set accordingly
• Maven 3.8.1+ installed

When using native image compilation, you will also need:

• GraalVM 19.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.

Compile and Run in Local Dev Mode

mvn clean compile quarkus:dev

NOTE: With dev mode of Quarkus you can take advantage of hot reload for business assets like processes, rules, decision tables and java code. No need to redeploy or restart your running application.

Package and Run in JVM mode

mvn clean package
java -jar target/quarkus-app/quarkus-run.jar

or on windows

mvn clean package
java -jar target\quarkus-app\quarkus-run.jar

Package and Run using Local Native Image

Note that this requires GRAALVM_HOME to point to a valid GraalVM installation

mvn clean package -Pnative

To run the generated native executable, generated in target/, execute

./target/process-business-rules-quarkus-runner

OpenAPI (Swagger) documentation

Specification at swagger.io

You can take a look at the OpenAPI definition - automatically generated and included in this service - to determine all available operations exposed by this service. For easy readability you can visualize the OpenAPI definition file using a UI tool like for example available Swagger UI.

In addition, various clients to interact with this service can be easily generated using this OpenAPI definition.

When running in either Quarkus Development or Native mode, we also leverage the Quarkus OpenAPI extension that exposes Swagger UI that you can use to look at available REST endpoints and send test requests.

Example Usage

Once the service is up and running we can invoke the REST endpoints and examine the logic.

Submit a request

To make use of this application it is as simple as putting a sending request to http://localhost:8080/persons with appropriate contents. See the following two cases:

Adult person

Given data:

{
  "person" : {
    "name" : "john",
    "age" : 20
  }
}

Submit the JSON object from above:

curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d '{"person" : {"name" : "john", "age" : 20}}' http://localhost:8080/persons

After the Curl command you should see a similar console log

{
    "id":"fd4f629d-6822-4ca2-a8a6-a74f5f81e83d",
    "person":{
        "name":"john",
        "age":20,
        "adult":true
    }
}

Because the person is evaluated as an adult, no outstanding tasks should be here for given person.

We can verify there is no task running for Children Handling using following command:

curl http://localhost:8080/persons/{uuid}/tasks

where uuid is the id returned in the previous step.

A Child

Given data:

{
    "person" : {
        "name" : "john",
        "age" : 5
    }
}

Submit the JSON object from above:

curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d '{"person" : {"name" : "john", "age" : 5}}' http://localhost:8080/persons

After the Curl command you should see a similar console log

{
    "id":"c59054b9-aa1d-4771-bc5e-40f8b32d3ff5",
    "person":{
        "name":"john",
        "age":5,
        "adult":false
    }
}

Because the person is not evaluated as an adult, there should be outstanding tasks for given person.

To verify there is a running task for Children

curl http://localhost:8080/persons/{uuid}/tasks

where uuid is the id returned from the preivous step.

Should return something like

[{"id":"c59054b9-aa1d-4771-bc5e-40f8b32d3ff5","name":"ChildrenHandling".....}]

Then to see the Task created perfor the following command

curl http://localhost:8080/persons/{uuid}/ChildrenHandling/{tuuid}

where uuid is persons id and tuuid is task id.

It should return something similar to

{
    "person":{
        "name":"john",
        "age":5,
        "adult":false
    },
    "id":"c59054b9-aa1d-4771-bc5e-40f8b32d3ff5",
    "name":"ChildrenHandling"
}

Then we can complete the task and validate child with

curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d '{}' http://localhost:8080/persons/{uuid}/ChildrenHandling/{tuuid}

Where uuid is persons id and tuuid is task id

Should return something similar to

{
    "id":"09f98756-b273-4ceb-9308-fae7cc423904",
    "person":{
        "name":"john",
        "age":5,
        "adult":false
    }
}

and there should be no outstanding task for the person anymore.

Deploying with Kogito Operator

In the operator directory you'll find the custom resources needed to deploy this example on OpenShift with the Kogito Operator.