Skip to main content

Oracle APEX Reporting Tips & Tricks - Book Review

Just after my not-so-positive previous book review, another author dared to ask me for my review. I asked him whether he was sure, and he - confidently - answered positive. This book, written by George Bara from Romania, is called "Oracle APEX Reporting Tips & Tricks", so - from the title -  it seems to be covering similar subjects as the previous one. 
Chapter 1, "Introducing APEX", covers the install of APEX and the creation of a first application. The good thing here is that the author doesn't rewrite the docs, but just links to them. Right after that he introduces the two main report types: the Classic Report and the Interactive Report.
Chapter 2, "Interactive Reports Basics", covers the cool options from the Action menu as well how a developer can dis- or enable these options. Also the Alternate and Icon view is explained, followed by a brief example on styling an IR using CSS. After that multiple download options are covered, including an extensive custom download format.
Chapter 3, "Advanced Interactive Reports", dives a little bit deeper (as you could expect with a title like that). Reports based on APEX collection as well as some neat tricks to get the current filtering settings from the APEX dictionary are explained.
Chapter 4, "Beyond Interactive Reports",  dives even deeper on the subject. Adding and managing checkboxes in reports and how you can use Dynamic Actions on these checkboxes is explained. This is followed by a few paragraphs on dynamic filtering (using the APEX_UTIL.IR_FILTER procedure). The last paragraph covers how you could show images in your report. In this chapter I am missing two things: The first is the option of filtering through URL parameters, as described here. The second one is the alternative for showing images, using the APEX Listener, as described in Kris' blog.    
Chapter 5, "Reporting on Web Services Results", explains how to create web services references and how to create a report on the results of a web service call.
Chapter 6, "PDF Report Printing", dives deep into Apache FOP with a lot of XLS-FO examples. Obviously the author has a lot of experience in this matter. As the final chapter, Chapter 7, "Complex Report PDF Printing", goes even deeper than that. Alas, other options for printing, like PL-PDF or even BI Publisher are not covered at the same depth. Also the more modern alternative (or replacement) for Apache FOP - using the APEX Listener for PDF printing - is not covered. In my opinion the book should get an update on that (as I never used all the XLS-FO tricks mentioned here myself)!

So as a conclusion, the book covers what it promises. Reporting and printing. Nothing more, nothing less. It is aimed at beginner to intermediate developers.
One (more) remark though. While reading you notice the book has lacked a proper editor review (it is self published). The author is not a native english speaker and that now and then that is noticeable - sort of similar when reading this blog ;-). There are some errors and sentences that don't flow smoothly. But if you go over that, it is a good book for a starting APEX developers (and for some parts for intermediate ones as well), who wants to know more about the reporting solution APEX offers.
Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

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…