Case Management Part 2: Anatomy of a Project

In Oracle BPM 11g PS6, BPM Studio (JDeveloper) is the design-time environment for Case Management. This blog entry will describe the make-up of a Case Management project in BPM Studio, stepping through all the terms and properties associated but will stop short of giving recommendations or best-practices, which will follow in a later blog entry.

BPM Studio: Case Management Project

  • One Case per BPM project.  

General Tab

  • Checkpoints in the progress of a Case
  • Logical grouping of deliverables – no direct activity or work associated

  • User-defined statuses on completion of a case

Data & Documents Tab

  • Data associated with the Case – user defined / XSD etc
  • Manually added in this tab for use within Case
  • Automatically added on creation of new case activity

  • Where the data associated with the Case is stored
  • Defaults to database
  • Oracle UCM & Alfresco CMIS as current alternatives (April 2013)

User Events Tab

  • Manual actions that can occur during the lifetime of a case which trigger events inside the case
  • An example would be – a fax arrives and a milestone can be marked as complete

Stakeholders & Permissions Tab

  • People involved in the processing of the Case – the case workers
  • Defined as a user, group, application role or process role
  • By default granted all available permissions on case objects, modifiable after deployment by Administrator….

  • Attached to case objects such as documents and data to define who has what kind of access to objects
  • CONFIDENTIAL & PUBLIC by default, can add custom permissions

Translation Tab

  • Allows localization of a Case and its case objects

Case Activities 

Represent specific work in the context of a case and can comprise....

  • A Human Task....

  • A BPMN Process....

  • Custom (java code)....

 Once created, Case Activities can be configured as follows....

  • Manual – activated from the UI
  • Automatic – activated by the engine on some condition
  • Required – must always be activated
  • Repeatable – can be activated more than once
  • Conditionally Available – only available to be manually or automatically activated depending on business rule
  • Permission – who has access to this activity ?

  • Determined by input & output of the human task or BPMN process if this case activity relates to these
  • Entered manually for custom activity

 Case Business Rules

  • Each Case has a business rules dictionary generated automatically
  • Rules can be added to the ruleset accordingly to control the flow of the case
  • Rules can be fired on every type of case event…
    • Life cycle events
    • Milestone events
    • Activity events
    • Data events
    • Document events
    • Comment events
    • User event

As an example, assume that once milestone “Returned” has been reached the activity “ChargeCustomer” should be activated….

Interacting With a Case - Proactively 

  • From the User Interface (see later blog entry)
  • Service call from composite artefact (BPM, mediator etc…)
  • API call
  • Available operations
    • abortCase
    • closeCase,
    • reopenCase
    • suspendCase,
    • resumeCase
    • attainMilestone
    • revokeMilestone

Interacting With a Case - Reactively

  • Event Delivery Network (EDN)
    • System events automatically generate EDN events....
      • case lifecycle
      • case activity lifecycle
      • Milestone
      • Document
      • Comment 
    • User events can be set to publish to EDN....

Coming Next 

Now that we have investigated the design-time for Case Management inside BPM Studio and understand the concepts behind it, we will move on to looking at a typical lifecycle of a simple Case Management project.



Excellent series. Can we expect more use cases, where Case Management can be used instead of traditional process approach ? Is there any plan to update Oracle Process Accelerators to show CM capabilities ?

Posted by guest on April 03, 2013 at 11:18 PM PDT #

Glad you like the series.... more to follow.

There will be further information on real-life use-cases, and I believe that Process Accelerators will also begin to use CM, although Product Management would have to verify this.

Posted by Mark Foster on April 04, 2013 at 02:52 AM PDT #


Thanks for response. It also would be great to publish on Oracle Learning Library page short screancast, how to implement ent-to-end CM with JDeveloper/BPM

Posted by Kuba on April 04, 2013 at 03:11 AM PDT #

Thanks for this introduction to Oracle BPM Suite 11g !
I did not have the time to experience the Case Management part of Oracle yet. I did have the opportunity to play with the Cordys BOP4 produkt for Case Management. So i used your blog item to compare Oracle with Cordys (
I think the biggest opportunity for Oracle is to make the Case Management milestones and activities more transparent. At the moment it can be hard to figure out what is going on behind the scenes because the business rules can be hard to read.
On the other hand the Oracle features are massive.

Looking forward to your next blog and also to Oracle 12c!

Posted by Roger on April 04, 2013 at 11:53 PM PDT #

Thanks for posting Roger... I had a read of your blog and I can understand where you're coming from with respect to design-time transparency.

I would say that this is just the first release of "Adaptive" Case Management in BPM 11g... the intention was to initially provide a fully functional runtime engine and API along with design-time tooling in BPM Studio.

Case Management will evolve through the coming releases... the plan is that at design-time it will utilize an industry standard view to visualize the case model. It will also evolve in terms of the runtime UI... watch this space for more details.

Posted by Mark Foster on April 05, 2013 at 12:30 AM PDT #

thanks for this great overview series. It's very helpful to get a first overview and understandig regarding case management etc.

Posted by Hubertus on May 17, 2013 at 04:19 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

This is the blog for the Oracle FMW Architects team fondly known as the A-Team. The A-Team is the central, technical, outbound team as part of the FMW Development organization working with Oracle's largest and most important customers. We support Oracle Sales, Consulting and Support when deep technical and architectural help is needed from Oracle Development.
Primarily this blog is tailored for SOA issues (BPEL, OSB, BPM, Adapters, CEP, B2B, JCAP)that are encountered by our team. Expect real solutions to customer problems, encountered during customer engagements.
We will highlight best practices, workarounds, architectural discussions, and discuss topics that are relevant in the SOA technical space today.


« July 2016