Jarvis Pizzeria: The Document Only Delivery Process

Let’s have a look at the Delivery Process of the Jarvis Pizzeria. In this blog post, we will explain the functionality of the Delivery Process with the help of the Document Only feature when creating a new process.

When we create a new process we can select the option ‘Document Only’ in the Create Process popup.

Document Only processes are for descriptive use only and are not part of the working and running application. It is a good way to setup a process to discuss with your peers, users, architects or anyone else. One of the advantages of starting a document only process is that it will not check whether it is valid or not, since it is for descriptive purposes only.

Continue reading


Jarvis Pizzeria: Functional description of the Payment process

Before we start preparing our pizza the order needs to be paid. With the implementation of the payment process we try to answer the following questions:

  • How do the business rules work in PCS and how do they differ from their on-premises counterpart?
  • What types of gateways do we have at our disposal?
  • Do we have multi-instance subprocesses?
  • How do we implement correlation?
  • And more…

Continue reading

Jarvis Pizzeria: Functional description of the Preparation process

Lets take a closer look at one of the stages of the Jarvis Pizzeria process, the second phase is the preparation process. The implementation is a simplified presentation of reality. The purpose of the blog is not implementing a true presentation of reality, but learning some PCS features in particular.

The learning objectives for the preparation part of our blog series are:

  • (Im)possibilities during the conversion of 12c on-premise to PCS. Determining alternatives for the impossibilities.
  • Starting a process via a SOAP User Interface (SoapUI).
  • Oracle Content and Experience Cloud (CEC) Integration. (Start a process via a Document, Archive the Order.)
  • Usage of a Decision Service, Correlation and more …
  • Transforming the Preparation process into a reusable subprocess

The image below is a view of the process we will implement.

Continue reading

Jarvis Pizzeria: Setting up the Jarvis 1.0 process

For the Jarvis pizzeria process we have distinguished three phases: payment, preparation and delivery. Hence, the main process is comprised of those three phases. Setting up the main process enables us to work together, because each one of us can implement a separate phase, without running into merge conflicts or whatsoever.

For creating a new process, click the plus icon in the application home screen.

Continue reading

Jarvis Pizzeria: PCS Integrations — Calling SOAP/REST Services

From within our process in Oracle Process Cloud Services, we can call different service types. We can call an Integration on the Oracle Integration Cloud (ICS), a SOAP endpoint or a REST service. However, before we can call the service we need to create an Integration within PCS. The name integration here is a bit confusing, because it does not refer to Integration from ICS, but a local integration within PCS.

On the left hand side, in the black menu, we can see the Integrations tab. When we click here, we go to the Integrations page. Here we can create the integrations to call from our process. As you can see, we can use ICS Integrations as well as SOAP or REST connectors. We will not discuss the ICS Integrations, but focus on the SOAP & REST connectors that we want to call.

Continue reading

Jarvis Pizzeria: Team Collaboration in PCS

An interesting aspect of working in Oracle Process Cloud Service with a team of three people is the fact that you need to collaborate and work together in the same “source”. However, where traditionally we are used to develop on our machine and merge source in repositories like Git, Bitbucket or Subversion, in the Cloud, we do not even see the source, let alone are able to merge it.

So, how does a team collaborate in the Oracle Cloud?

Oracle offers a good, free platform for collaboration called Developer Cloud Services (DevCS).

As long as you have an other Oracle Cloud product – i.e. JCS, ABCS – DevCS comes for free, it does not come stand-alone. Within this environment, it offers a wiki, issue trackers, source control and much more. For this use case, we will focus on how to work together within PCS.

Continue reading