Recently I did a POC with BAM 12c at the customer. In a series of post’s I will describe my findings/experiences.
In the first post of this series I described the initial situation (Impact of ACM Implementation on BAM). This post ended up with the following challenge.
We have a ACM Case consisting of about thirty Case Activities. The Case and the individual Case Activities are housed in a private composite (1 + ~30 composites).
Challenge: How can we group/filter in BAM by ‘specific’ metrics that are present in each composite. For example ‘Department’.
In the second post (Filtering/grouping in BAM by ‘specific’ metrics (explored solutions)) I have 10 recognized/examined solutions appointed for this challenge. In this third post one of these solutions (number 9) is further developed.
‘Use of a dummy Data Object based on the generic format supplemented by the generic custom indicators. This for both activity and process’ data. Customizing the generated dummy view on the database by merging the various generated views we more or less fool BAM.’
We start by making a ‘dummy’ data object in BAM. This data object is based on the generic activity data object. Read the complete 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.