Jarvis Pizzeria: First step in Implementing the Order Processing, Interface Definition

In post Functional description of the pizza preparation process we gave a functional description of the pizza preparation process. For this we used the image below. Till now we only have implemented the bottom part ‘the preparation of a single pizza’.

In this post we will do the next step. The preparation of a complete order, containing potentially multiple pizzas. We will do this in a separate process. So let’s start by creating a new process in the preparation application. We gave it the self explaining name OrderPreparationProcess. Continue reading

Advertisements

Jarvis Pizzeria: Deploying and reverting to Snapshots

When working on a PCS application, you save and publish your changes often. However, when you publish a certain state of the application, you can decide to create a snapshot of this state of the application.
This can be very helpful if the publish represents a certain version of the application. Later these snapshots can be deployed or reverted to in case you want to roll back to a previous version. It is also possible to see what was in the application at the time of the snapshot creation.
In this blog we will show you how to work with snapshots.

When publishing, in the popup on the right hand side there is a option to ‘Make Snapshot’, when this checkbox is checked you can enter a name for the snapshot, in this case the snapshot will represent Jarvis 1.0!

Continue reading

Jarvis Pizzeria: Different presentations for same WebForm

Different presentations for same WebForm

In post (Workaround for XSD list-element issue in WebForm) we created a default WebForm for the Pizza Preparation process. In each human interaction of the process we used this default WebForm with the default presentation. In this post we will create a different presentation for each human interaction in the process..

  1. Crust Preparation Will only show the pizza name and size. Both fields are
    editable.
  2. Filling the Pizza Shows alle data. The pizza name and size are read-only. The
    ingredients are editable. It’s also possible to add or remove
    ingredients.
  3. Put in Oven All data is shown read-only.
  4. Get out the Oven The Pizza naam and size are shown read-only.

As a starting point for this blog, we use the end result of the above mentioned blog. We begin by adding presentations to the IngredientsWebForm. Continue reading

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

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