Skip to main content

APEX and Google Visualizations: Create sub-zero dashboards

APEX is cool, Google is cool, Google Visualizations are even cooler. So the combination the coolest technologies available is sub-zero!
A Google Visualization needs can get it's data programmatically by using javascript: create a DataTable object and use addColumn to define the columns and addRows to define the rows. But a Visualization can also be fed with a JSON object. So I created a package prodcure that reads a sql query and spits out a JSON string in the format Google likes. This procedure is called by an APEX On Demand Application Process.
In every APEX page the necessary Google Visualization packages are loaded by calling google.load with some packages, like this:

google.load('visualization', '1', {packages :[ 'geomap', 'intensitymap', 'map' ]});
(The google.load function is loaded in the template by referencing a javascript file http://www.google.com/jsapi).
Every chart is defined as an HTML Region. The source of that Region contains a SQL Statement embedded in a DIV.

<div id="geomap">select 'US-'||cust_state state, sum(order_total) OrderTotal
from demo_customers c, demo_orders o
where o.customer_id = c.customer_id
group by cust_state</div>
In the Region Footer the JSON string is pulled using a getData function. That function calls the PL/SQL JSON-generator procedure that fetches the SQL query from the APEX Repository. Subsequently two simple calls are enough to replacing the SQL query with the Google chart.

<script type="text/javascript">
$s('geomap',null)
var data = getData('#REGION_ID#');
var geomap = new google.visualization.GeoMap($x('geomap'));
var options = {};
options['region'] = 'US';
options['width'] = '300px';
options['height'] = '300px';
geomap.draw(data, options);
</script>
On the Google Visualization website the expected data (number of columns and type) are described for every type of chart. By just entering a SQL Statement that corresponds with the Google specs, I can produce any Google Visualization within seconds (once the SQL is correct ;-) )!
You can experience the APEX-Google Visualization live on apex.oracle.com.

Why would you use Google Visualizations (apart from "just because we can")? If your needs are fulfilled using the standard APEX / AnyChart stuff, there is no need. But there are some charts, especially the animated, time related, charts that are sooo cool and AnyCharts doesn't contain all the charts Google does (and vice versa). And I guess the number of Google Visualizations will grow, as everyone can add gadgets to that library.
8 comments

Popular posts from this blog

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…