Jarvis Pizzeria: Notification Task in PCS

So far we have covered most standard components of the PCS suite. However, we haven’t looked at the “Notification Task” in-depth yet. We have used the on-premises variant at various projects but it was the hassle of setting up the User Messaging Service (UMS) that made you reluctant to use this feature on beforehand. Will the PCS variant be a gamechanger? Let’s find out!

We implemented a basic process with a standard notification task and configured it to send an email to marc.kuijpers@rubix.nl. The implementation details are shown below:

Continue reading

Advertisements

Jarvis Pizzeria: Workaround for XSD list-element issue in WebForm

Workaround for XSD issue in WebForm

In an earlier post (Using an imported XSD in PCS) we have made notices that it is not possible to create a Webform based on a xsd-type that contains a list elements. In our case a list of pizza ingredients.

In this post we will give an alternative way to create a webform that displays the data, including the list of ingredients. Continue reading

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. Continue reading

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

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