BPM is the place where IT and the business meet. But what good is IT if the customer is unhappy? It doesn’t matter whether we’re talking about internal or external customers, a poor customer experience eventually means lost revenue—while a good experience means increased competitive advantage.
Oracle BPM 12c has a new feature included that allows for BPM scripting using the Groovy language. This was missing in BPM 11g and is very similar to the feature that was available in BPM 10g that allowed for BPM scripting using its own scripting language - PBL (Process Business Language). There are two primary places you can use Groovy in 12c:
Have you ever completed a software project and had nothing go wrong? Neither have I. Projects using Oracle’s SOA Suite are no different than Java projects and you will need to debug issues at some point.
Here are five tools for debugging issues on Oracle SOA Suite:
A very common use case for using an SLA (Service Level Agreement) is when there is a start date-time (not necessarily the current date-time) and an end date-time and you want to use the time difference between those two dates as your SLA in your BPM process. In the good old BPM 10g days you could do that easily. You could take the two dates and subtract one from the other and the result could be used as a SLA value. Unfortunately, the same cannot be done in BPM 11g as easily but we do have a solution.
Everyone getting started with Oracle BPM struggles getting the link for a process's Initiator task to appear in the Workspace's Applications tab. This covers the six most common reasons this occurs and instructions on how each is resolved.