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