Jarvis Pizzeria: Using an imported XSD in PCS

In this blog post we mention issues with enums and the usage of imported types on web forms. This was on version '17.2.3'. A re-test on '18.1.3' proved that the issues have been solved. 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. Create a New Web Form

Give the Form a name and click the Create button.

Because the ‘Open Immediately’ check is on, the new Form opens. In the bottom right corner is the Business Types Palette. In here we see the imported Business Types that are based on the used xsd. For this form we need the PizzaPreparationBO. Drag and Drop this on the canvas.

The following form is generated. All elements of the business type are there. The ingredients are placed in a repeatable section.

Although the form is not very beautiful yet, for now, we let it be what it is. We're going to test first before we make the form look better.

Save the form and open the created process to connect the form to the tasks.

We have attached the same form to all tasks in the process. After that open the Data Association for the task. The images below show the input and output mapping used for the ‘Prepare Pizza Crust’ task.

Save and Publish the application.

Enter a comment (it’s mandatory).

Next we Deploy the application.

Details about the deployment of an application can be found in a separate Jarvis blog and starting an instance with SoapUI can be found be found in another Jarvis blog.

After running a test with SoapUI a new running instance is created. On the tasks page the first task of the running instance can be found.

Open the task by clicking on it. The task opens. But to our surprise, not all data is there. The list of ingredients is missing.

Let’s analyse this a bit further. For this go to the tracking page. The instance can also be found there.

Open it by clicking on it. The Graphical view shows that the first task is currently active.

Switch to the Tree view.

Then select the task payload (instance entered the activity). It might be a surprise but the list with ingredients is send to the task, so why is it not displayed?

Is it a bug in the used version (17.2.3)? And will it be fixed in a later release? Or is it a design decision? Only time can tell.

In a coming blog we will describe a way to overcome this issue.