Using the SOAP interface to start a Process

We as old-fashioned SOA/BPM Suite developers, are used to test deployed services using tools like SoapUI. In this blog post, we will show you how to start a Process in the Oracle Process Cloud from the SOAP UI interface.

On premises with SOA or BPM we used to start by obtaining the required wsdl from the Enterprise Manager.

Continue reading

Advertisements

Jarvis Pizzeria: Using a Decision Model in the Delivery Process

To make the delivery of the pizzas to our customer, we need to decide how to deliver the pizzas. In our process we’ve already got the order data, so we know what the order is and where it needs to be delivered, but what is the best way to deliver the pizzas?

We will create a decision model in PCS to help us with this decision. In the delivery process we will call the decision model like a service and use the answer to make the correct decision.

The input for the decision model will be the amount of pizzas and the distance to the customer. Based on these data we will decide to either use a bike, moped or car to do the delivery. A very common decision to make in the Netherlands, since we love our bikes and often deliver pizzas by bike rather than by car.

We start with going to the PCS home. All the way out of the jarvis application and on this home menu we click the create button. Here we see that besides new applications, we can also create a new decision model. This means the decision is not coupled directly to the application with our processes, but it is a stand alone decision model. Continue reading

Jarvis Pizzeria: Implement rules

When the order comes in, payment needs to be made first before we start preparing the pizza. Our order payment process supports three possible payment options:

  • Creditcard: obviously a commonly accepted payment option
  • Cash: although we are a very tech-savvy company we would also like our old-fashioned customers to be able to pay the pizza with cash money
  • Deferred payment: our most trusted customers can pay their order in a deferred way. Deferred payment means the customer receives an invoice per email and is asked to pay the order within two weeks.

The payment process is depicted below. The first activity in the process is concerned with determining which payment options are available. What component can we use to insert some facts, start reasoning about those facts and give us an answer based on those facts? Of course…Oracle’s own business rules!

Continue reading

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