Jarvis Pizzeria blog refresh part 1 of 3 by Marcel van de Glind
In this blog I do a quick refresh of the first 13 Jarvis Pizzeria blog posts (note: the different headers in this blog contain a link to the actual blog).
This is the introduction to the blog series in which the original team is introduced and the scope of the blogs is indicated.
As stated before (Jarvis Pizzeria is back again), the scope has been extended from PCS only to the entire OIC. But this refresh is only about PCS (because that was the former scope). So also the solutions that we describe that we would do differently nowaday with the complete OIC toolbox. ICS and VBCS will be added more and more visibly over time in new posts.
The purpose of this blog is to find out the team collaboration capabilities of PCS. In this field nothing has really changed in itself during the last year. I think that this already works fine, so changes are not really necessary.
In the initial blog we states the following:
“It looks like the saved, but not yet published, changes within the application are automatically published, since we verified that the user taking over the lock directly sees those changes. But this might not be the desired behaviour.”
I assume that this behavior was an error, that has been resolved as a recent test has shown.
In this blog we demonstrated the creation and use of both a SOAP and a REST service in PCS (not yet in ICS, that will certainly be shown in a new blog later on).
The purpose of the blog is to try out / demonstrate the various options for starting a process. In the structured process we start the 3 pizzeria sub-processes in different ways. Read the complete article here.
For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.