Jarvis Pizzeria: Handling SOAP Faults in PCS

As we are very optimistic developer we started out with modeling and testing the happy flow of our Jarvis pizzeria. But as experience learns it is the big bad world that obliges us to deal with both expected and unexpected failures. This blog post we will look into the handling of SOAP faults that PCS has to offer out-of-the-box.

As a starting point we have created a basic process with one service call:

This SOAP Fault service is connected to mockable.io service that is configured to throw back a remote fault, i.e. the invoked service endpoint cannot be reached. Let’s deploy the process, start an instance and see in the workspace what has happened.

Note: to use the OOTB error handling leave the fault policy checkbox marked during deployment:

Continue reading

Advertisements

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.

Continue reading

Jarvis Pizzeria: Using an imported XSD in PCS

In the post  Import the 12c On-premises Preparation Process we saw the Business Types that were imported (also shown here)

We already stated that we had an issue with enumerations. But is this the only issue with the xsd? Unfortunately not, as will become clear soon.

Making task forms was not part of the import blog, however, in this blog we are going to do this. We will do this based on the imported xsd. So let’s get started.

Continue reading

Jarvis Pizzeria: Deployment and using the workspace

Having played around with all the features PCS has to offer it is now time to see some action. In this blog we will show you how to deploy your application, start the application and see how it behaves within the workspace.

But first of all, we need to have a application that is ready to deploy. In other words, our minimal deployable product consists of an application without any errors. Pressing the validate button in the top-right corner will tell you the current state of the implementation.

Unfortunately, we ran into a bunch of errors! Mostly due to missing implementations of service calls. The good thing however is the “Fix” link.

In contrast to JDeveloper, clicking the “Fix”-link will bring you directly to the – in this scenario – properties screen to fix the issue. Oops, we forgot to select a ruleset for our business rule activity.

Continue reading

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.

Continue reading