Best Practices from Oracle Development's A‑Team

BPM 11g - Case Management Part 3: Runtime Lifecycle of a Project

Mark Foster

Now that we understand what Case Management is and the anatomy of an Oracle BPM 11g PS6 Case Management project, we can look at the simplified lifecycle of a project at runtime.... how the stakeholder interacts, what happens when a Case Activity is triggered, what happens when it ends etc....

Step 1: Stakeholder triggers Case Start from User Interface (or other)

Step 2: Any Case Data entered by Stakeholder populated

Step 3: Case Start Event generated

Step 4: Case Event triggers Case Rules

Step 5, 6 & 7: Case Rules trigger Human Activity, BPM Process, Custom Activity etc... and Engine populates Case Data

Step 8: Relevant Activity Start Event(s) generated

Step 9: Stakeholder (via UI) or other Subscribes to Case Event

Steps 10 Onwards: Case Continues as above to completion

We can see from the above that the lifecycle, although not complex, is very powerful and provides all interactions necessary to manage a Case at runtime.

Coming Next

Now that we have seen how a Case Management project behaves at runtime, we can start to look at best practices around the design of a Case Management project to help with performance, usability, management etc...


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha