Oracle BPM’s Multi-instance Subprocess is a type of a subprocess activity that can take an array of items as input and then handle each individual item in the array separately. The number of times the subprocess is executed can be determined at runtime by the size of the array at runtime. Each work item that is spawned is then acted on individually.
A typical use case for this is when you have an order with many order items inside of it. If each inidivdual order item needs some kind of approval or handling, consider doing this using Oracle BPM’s BPMN based Multi-instance Subprocess activity…
Red Mavericks’ blog published an article on the Process Data definition. “We have our BPMN process and if we only want to document our process, this is almost all the work we’ll need to do. However, Akino Fishing Co. wants to not only document, but also automate and execute the processes. For that, we need to define our process data.”
Want to sharpen your BPM skills? Settle in for an educational video binge these free tutorials from Oracle University:
Getting Started with BPM – Episode 1: BPMN Overview [40 minutes] Meera Srinivasan, Director of Product Management for Oracle Business Process Management Suite, explains how Oracle BPM Suite uses BPMN models for process design and analysis. She then describes the four major groups of BPMN constructs: activities, gateways, events, and subprocesses.
Business Process Management (BPM) and Service-Oriented Architecture (SOA) provide enterprise-level IT environments the benefits of flexibility, versatility, and a relative ease-of-use that makes BPM attractive to business managers and SOA to IT executives. BPM has become the go-to solution for optimizing a wide range of business processes and improving an organization’s efficiency and agility. BPM’s popularity is due in large part to the way it can seamlessly integrate a variety of human, document, and system-based processes to streamline and simplify the enterprise ecosystem and make businesses more agile, responsive, and competitive. But what makes it especially attractive is the capability it provides non-technical employees to alter software processes and change rules without having to delve into coding.
SOA , on the other hand, provides organizational flexibility much like BPM, but on a fundamental infrastructure level. Simply put, it lowers software development and management costs by providing the ability to create reusable software modules. SOA, by its very nature, enables simple services to be combined to make more complex ones with increased functionality, while speeding development and time-to-implementation. Given their similarities, it stands to reason that if BPM and SOA are valuable on their own, they’re even more valuable together. However, it can be a hard sell because the two methodologies seem, on the surface, to be somewhat redundant and integration (along with the cost) unnecessary.
Business Processes implemented in BPEL and BPM(N) and running on Oracle BPM Suite 12c or SOA Suite 12c have to fulfill a business purpose and as such must meet business requirements – both functionally and non-functionally. SLAs for throughput, response time, quality are usually associated with these processes and we typically also would like insight in the number of process executions (per group) and the paths taken through our processes.
This presentation introduces process analytics in both BPEL and BPM processes in Oracle SOA Suite and BPM Suite 12c. It explains how to configure out of the box generic analytics and process specific business indicators. The presentation than introduces BAM 12c. It demonstrates the out of the box process analytics reports and dashboards. Then it explains how to create custom reports on the unified process analytics star schema or on custom tables. Finally the presentation goes into real-time monitoring in BAM using JMS and enterprise message resources in combination with the event processing templates in BAM.
On August 20th, the fourth Bundle Patch (patch id 21640312) was released for BPM Suite 12.1.3. The notes unfortunately specify: This patch is mutually exclusive with all SOA Bundle Patches after SOA Bundle Patch 1. For example, if you attempt to apply this patch on top of SOA Bundle Patch 2, all fixes from SOA Bundle Patch 2 will be rolled back.