|In this blog I do a quick refresh of the third (and last) batch of 13 Jarvis Pizzeria blog posts (note: the different headers in this blog contain a link to the actual blog).|
The core of this post concerns the release of Oracle Integration Cloud, the bundling of Process Cloud Service (PCS), Integration Cloud Service (ICS) and Visual Builder Cloud Service (VBCS). and the addition of Dynamic Processes to PCS.
Recently Rick Kelder, my new Jarvis Pizzeria partner, wrote an extensive blog about the status of OIC according to his opinion (oic-oracle-integration-cloud-what-is-it?).
This introductory blog consists of an overview of the different parts of Dynamic Processes. This is done via the default sample tour of Oracle PCS.
In this blog we set the skeleton for the Pizzeria Dynamic Process. We define the different phase, activities, tasks and milestones.
Besides that we found out that the standard Oracle example tour cannot be saved as a starting point for further work. However, the save button is available, suggesting that this is possible. Oracle this is a bit confusing.
In this blog we connect processes and task to the activities created in the skeleton of the dynamic process of the previous blog.
We show how things look-like on runtime for running and also completed instances. OIC gives a good out of the box representation of the dynamic process. We can work on the process within the OIC and have an overview of what happened with the process. We see the progression, stages, activities and can drill in the audit trail.
In the previous blog we have had a look at the runtime. We ended with the situation that all activities are becoming available at once and we can work on everything together. In this post we start modifying this flow. We handle the stages. Work with milestones and use condition when activities can be started or are enabled.
In this blog we discuss the different expression variants in a Decision Model. Here the Expression, If-Then-Else, Decision table, Context, List, Relation and Function are discussed. After we have posted the original blog, an expression variant has been added, namely the Loop.
In this post we make a complex decision model that determines the order of preparation of the pizzas in an order. The order of preparation is determined by the baking time, the total preparation time of each pizza and the number of available ovens (1 pizza per oven).
In the decision model we make use of the various expression as described in the previous blog. The final result is a fairly complex model in which we touch many different possibilities of the FEEL expression language.
In this post we describe the features of the mobile app. According to the table of differences, it would not be possible to view the dashboard. But this was and still is possible on an iPad. Our former conclusion still stands:
the mobile app is a very useful application for the end user.
During the PaaS forum in Budapest we as a Jarvis team were given the opportunity to give a presentation about our blog series and specifically about Dynamic Processes and to our surprise we were awarded the Partner Community Award for outstanding PCS contributions.
In this blog we show an example of how Markers and Conditions can be used in PCS. We also describe what Markers and Conditions are. This is summarized below.
For Dynamic Processes we recognize the following markers:
- Repeatable: controls whether a stage, activity or milestone is repeatable.
- Auto Complete: controls the completion of a stage instance.
- Manually Activated: controls the activation of a stage or activity instance.
- Required: controls whether a stage, activity or milestone is required.
Next we have the following conditions:
- Activation: additional entry criteria for a stage.
- Enablement: additional entry criteria for a activity.
- Termination: additional exit criteria for a stage or activity.
- Completion: addition exit criteria for a milestone.
In this blog we will take a look at the way a dynamic process deals with a process that ends with an exception. Our findings:
“The Dynamic Process can’t handle two different callbacks. So if you would like to model a scenario in which the process aborts and the case should act upon the abort, you should work with case data to indicate the process ended not successfully. This also means that you should think about making processes repeatable to ensure that an aborted process can start again.”
In this blog we show the out of the box dashboards in PCS that you can use to monitor your instance. We also show how to create custom System Reports.
In this blog we show how to create custom reports based on user defined indicators. There are three types of indicators that you can create:
- A Dimension represents the grouping on the X axis,
- A Measure will be the value of the Y Axis.
- An Attribute, in turn, will act as a filter.
You can define customer indicators that you can bind to any data objects available in your process. They will become available for reporting alongside with the default system indicators.
This brings me to the end of this blog and the era of the first generation of Jarvis Pizzeria. On to a new series of Jarvis Pizzeria blogs about OIC (instead of just PCS) together with Rick Keller.