During Oracle Open World 2016, the latest release of Oracle Process Cloud Service got presented. The product has been making huge progress in all aspects, so here’s an overview of all the new and improved features.
Oracle Process Cloud Service
For those of you unfamiliar with the product: Oracle Process Cloud Service (PCS) is Oracle’s BPM solution for the cloud. While development on Oracle BPM Suite has pretty much come to an end, Oracle Process Cloud Service is the way forward and the platform for all new features related to Business Process Management. This meant that the product that was originally positioned as BPM for the citizen developer had to improve and mature to a full-blown BPM solution. It needs to support long running processes, improve its integration strategy and support case management, to mention some important subjects. While case management is not there yet, it will certainly come to Oracle Process Cloud Service and many other features are already there with the latest release.
As it used to be, modelling processes is done in the browser. This makes it easy for business and IT to collaborate on processes, because you only need an internet connection to get access. No need for development tools, code repositories and a powerful work station to get started. The main improvement in the process modelling is that Oracle has abandoned the usage of Flash. This makes the process modeller faster and easier to use, creating a far more pleasant and performant development experience.
When creating a Service Call, whether it’s synchronous or asynchronous, you can now select an Integration from Oracle Integration Cloud Service. Obviously, this is much more practical than dealing with WSDL imports and all the technical stuff related to that, but it also has a bigger meaning. It’s clearly showing that Integration Cloud Service has been strategically positioned as the way to go for process integrations. It’s putting the technical know-how of integration where it belongs, so you will no longer feel tempted to take that kind of complexity into a business process. Therefore, I strongly recommend following this approach as suggested by Oracle, instead of trying to work out your own integrations in PCS. Use these products for their purpose.
Oracle Process Cloud Service is still closely connected to Oracle Documents Cloud Service. It was already possible to deal with documents in your processes very easily, but now processes can even be started by putting a document in a certain folder in Documents Cloud Service. It requires minimal configuration on the Documents side, while in PCS you can now use a “Document Start” event for your process.
One important missing feature in PCS was correlation. This feature is there now, so you don’t have to use BPM Suite anymore for your long running, asynchronous interactions with other processes and services. You can use the “Message Catch” event to catch messages with the related correlationId that you have defined. This can be especially handy in cases of migrating your long running processes to a newer version.
If you want to start fast and you’re using relatively standard processes in your business, you can use QuickStart Apps. Currently, there are 6 of those available and I expect more to come in the future. It could also be nice if these could be purchased from the Marketplace.
You can now embed your process forms in other applications, for example various SaaS products. This will help you to create a seamless integration between your processes and other apps.
BI Cloud Integration
PCS is now integrated with Oracle BI Cloud, where you can use your default or custom analytics. While PCS also has dashboards, they are more for operational information, so this is a nice and much needed extra functionality.
Just like in BPM Suite, you can take actions in your processes directly from e-mail messages now. Reusable e-mail templates can be created, in which you can embed process data and actions for users to be taken.
What does the future hold?
I think that september’s release has been the biggest one so far for Oracle Process Cloud Service. However, the development team isn’t nearly done yet. Most noticeably on the agenda, there are the new business rule component, as a microservice and based on DMN (Decision Model and Notation), as well as Case Management, which should logically be based on CMMN (Case Management Model and Notation) and hopefully be less complicated than Case Management in BPM Suite. I believe that PCS has grown to be a mature product that can tackle most of your BPM needs already and with the two mentioned additions, it will be ready to fully replace Oracle BPM Suite in a more business-friendly and less technical manner. While not being a trendsetter in the world of BPM, at least Oracle is catching up quickly with modern developments and adding value by seemless integration with other Oracle cloud products.