By JuergenKress on Nov 21, 2013
In the previous blog entry we started to look at case artefacts, specifically case activities and how we should design these at the correct level of granularity.
In this entry we’ll look at case rules, the “glue” that connects case artefacts together at the level of the case.
Case Artefacts & Case Rules
As of PS6, the design-time for Case Management inside Business Process Management Studio has no “holistic” view of the case and its artefacts, however this is planned for a future release. In the absence of this I’ve been trying to understand how it would be possible to visualize everything that makes up a case and how these things are interrelated.
A Mind Mapping Approach
My colleagues Prasen Palvankar & Ravi Rangaswamy came up with a neat use of mind-mapping to show the case & its relationships.
… I find this great for understanding the questions that need to be asked in the design of a case from within Business Process Management Studio…”who are the stakeholders”, “what are the case activities”, “which documents can be attached to the case” etc. but from this I could still not immediately grasp what my case looked like and the relationship between the artefacts. Read the full article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.