As usual I first start with a piece of theory from the oracle documentation.
A business view is a visual representation of data fetched by a business query or one or more KPIs. In most views, numeric data fields, called measures, are grouped by non-numeric data fields, called dimensions. For example, lawsuit costs, a measure, can be grouped by department, a dimension. An aggregation is a computation based on multiple values in a data field, such as a sum or average.
Oracle BAM uses various view types:
- Graph Views
- Chart Views
- Table Views
- Gauge Views
- Geo Map View
- Treemap View
- KPI Watchlist View
Area Chart, Bar Chart, Horizontal Bar Chart, Line Chart, Pie Chart, Combo Chart, Scatter Chart, and Bubble Chart views are collectively called chart views. There are corresponding graph view variations of each of these views.
Some graph views are switchable. They can be changed to a compatible type. Provided that queries are compatible, some views are switchable with each other. These are Area, Bar, Horizontal Bar, Line, Pie, and Combo views. Gauge views are switchable within the category.
You can format views in many ways, changing colors, fonts, labels, thresholds, and other properties.
You can configure view characteristics that can be changed dynamically at runtime. You can configure how users can display more detailed data, which is called drilling. You can configure actions that the end user can perform on the view. You can also configure active data, which changes the query on which the view is based to a continuous query.
The table below shows the different categories and types. In the dashboards that I eventually will make only the marked types are used.
So let’s get into the implementation. In a random order I will describe the different views.
First the Treemap. This treemap is based on the ‘Organizational Tasks – Tree Model’ query. As a value (the size of the box) I took the average time a task is open.
Most interesting part of this view is that I have setup thresholds for each organisational level.
I also added a runtime interaction Action Button, just to find out how to use this. There are four different kind of action buttons available.
In this example I chose for ‘Show Confirmation Message’. In my dashboards (BAM Dashboards) post I will come back to this.
Next the Gauge. The gauge is based on the ‘Number Of Open Tasks Issue – Group SQL’ query. The view is pretty simple. Where I especially am interested in is whether it is possible to adjust the view on runtime (on design-time is in any case possible). In the dashboards post I will report my findings.
After the Gauge, I get to the Table View. In the dashboard I used the List and the Pivot Table variant. In Today’s and Yesterday’s Summary List I used the option to drill to the details. See the following three screenshots.
Drilling enables using to select an item in a series and view data at a more detailed level. Active data stops during drilling and then restarts. The following drilling types are supported:
- Drill Down
- displaying data one level down the drill path in the same view
- Drill Up
- displaying data one level up the drill path. You can only drill up if you have previously drilled down
- Drill Through
- displaying the actual data rows at the lowest level of the drill path in a List view
- Drill Across
- means opening a target dashboard or URL in a new browser window
A Pivot Table combines rows and columns to display a multi-dimensional view of aggregated data values. A Pivot Table is summarized vertically and horizontally for columns and rows. It is not possible to go to the details by clicking in a pivot table, so while this was possible in the list.
The next table view I have used is the ‘Days Open List’. This view is based on the ‘Days Open Task List – Flat SQL’.
This view has some interesting things. First the duration Icon column. This content of this column is displayed as html. And there is an invisible column Task Url.
The duration Icon CalculatedField contains a piece of html with a referent to the image shown in this column. This image is one of the custom images I added as described in my BAM Calculated Fields post. And the task Url I used in the runtime interaction definition:
I have defined a reference to the weblogic server containing the BPM humantasks (URL field). Next I specified a number of contant values. These values are part of the Task endpoint URL. In a live situation, some of these values should probably be variable instead of constant. The use of variables during the POC have I limited to a single item (taskUrl at the bottom) so I would be able to prove the concept. In the POC the value of this variable also comes from a Calculated Field.
In this graph I also make use of ‘Active Data’. Active data continuously aggregates data or displays a segment of data within a defined time window. As time passes in a time window, older data is removed from the view and newer data is added. Active data is supported only for basic Area, Bar, Line, Combo, Pie, Scatter, and Bubble views. None of the other variations of these view types support active data. However, active data is supported for all variations of Gauge views and for Point Theme and GPS Theme Geo Map views. Active data is not supported for Horizontal Bar, KPI Watchlist, Treemap, or Color Theme Geo Map views.
Active data is not supported for external data objects.
The last table view I used is Logo’s. I used this view, based on a flat SQL query to display a different Image depending on a data value. I have configured this in a way that for each jurisdictional organization another logo is shown. Column is displayed as html. Further there is nothing special for this view.
Next graph I used is the Pie. This view shows the average processing time per task for each judicial organization.
In this view, I used feature, such as Drill to Details, that I already have used in other views. Also tried several Pie specific presentation features. Findings here come’s later in the Dashboards post.
And finally the Line graph. I used this graph to gain insight into the number of tasks that is opened and closed daily. By selecting a specific point on the graph it is possible to see the details (drill down) of that moment in time. Again only repeated the use of some previously used features.
This brings me to the end of this post.
We start to approach the end of the blog series. We are almost arrived at the dashboards. But before it so far there are first still two smaller subjects (parameters and alerts). In the next post I will treat the parameters.
You can dowload the BAM project (including DO’s, Queries, KPI’s and Views) here.