Jarvis Pizzeria: Human Tasks – Design First WebForms

To create simple Human Tasks we use web forms in Process Cloud Service (PCS). Within the Delivery Process of the Jarvis Pizzeria, we are going to implement the HT for ‘Try Contacting the Customer’. This human task should become available after we have checked that the Customer is not a member and we do not know his email address.

Try contacting the non-regular / member from Jarvis Pizzeria, in the swimlane of the CallCenter.

We will take the Design First approach, meaning we will design the form and know what data objects we need afterwards, instead of looking at the data we need for the Human Task first.

Jarvis Pizzeria: Testing in PCS against the Development or Production environment

Within PCS there are actually two different environments, a development environment and the production environment. Once you have deployed your application it is available in the production environment as a certain version of the application. However, you might want to test your application before you deploy a new version. You can also test your environment against the so called ‘development environment’.

The blue button bar has a Test as well as an Deploy button on the top right.

Jarvis Pizzeria: Using the REST interface to start a Process

In the previous blog, we already explained how you can start your process from a SOAP interface. It is also possible to do this with a REST call. For this you need to find out a couple of things about your process after which you can do a post on the Oracle API to start the process. You can use any REST client you want, in this example we use Postman.

First of all, you need to query the process definitions API. This can be found by putting /bpm/api/4.0/process-definitions after the baseUrl, in our example:

https://pcs-jarvis18.process.us2.oraclecloud.com/bpm/api/4.0/process-definitions

Luckily PCS does not allow just anyone to see this information. We need to use Basic Auth and enter our username and password.