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.

Comments

Popular posts from this blog

Filtering in the APEX Interactive Grid

Remember Oracle Forms?

One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that.

In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the APEX_IR.ADD_FILTER procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically?

Start with creating an Interactive Grid based upon the good old Employees tab…

Adding items to your Interactive Grid Toolbar

The APEX Interactive Grid uses the Toolbar widget to create the default Toolbar showing the Search box, Actions menu, Save button etc. And since quite a while there is a nice Plugin "Extend IG Toolbar" by Marko Goricki that makes it very easy to add additional buttons to the Toolbar.

But what if you need more than a button? 
Inspecting the contents of widget.toolbar.js, you can easily spot there can be added more to the Toolbar than just a button: The type of control, available values:
"STATIC", "TEXT", "SELECT", "BUTTON", "MENU", "RADIO_GROUP", "TOGGLE".
The first example will show a way to easily switch from one filter to another. Of course we could use the standard functionality and create two different Report views, but using a Radio Group on the Toolbar gives a more "Tab" like user experience.

So how can we create a Radio Group that looks like a switch in the Toolbar?
In the Javascript Code …

Using Static Files in APEX has never been easier !

Almost every APEX Developer knows that JavaScript and CSS belongs in separate files and (in 99% of the use cases) not somewhere in your Page properties. If you have this code in separate files it is easier to use them in a Version Control System (SVN or Git) - if the files are outside of APEX. And the code you store in these files can be reused, in contrast to the stuff you store on Page level.In a lot of environments it is harder to use external files, because deployment of these files to the appropriate location on a webserver requires special privileges that not everybody has. In those cases storing these files as Static Application Files or Static Workspace Files might be a better solution. It makes deployment easier, because these files will be exported and imported as part of the application. You can't accidentally forget about them. But working with these files is quite a pain. When you need to edit something you have to download that file, make the changes, upload it again …