Skip to main content

KScope 11 - Sunday

The first day (or pre-conference day) was filled with four full day Symposium sessions. The APEX one I attended was completely filled by the APEX Development team itself. 
Joel Kallman kicked the day off with a nice story about the development of APEX, the tools they used etc. Then there where three more sessions about Tablular Forms, Interactive Report and Webservices - all pointing out the new APEX 4.1 features. 
The coolest one of the day was Marc'Sewtz's presentation on APEX for Mobile Devices. He showed that, using HTML 5 in your template, you can create real native-looking applications for mobile devices. You can already do that using the current version of APEX, but the 4.1 will also contain support for special mobile actions, like rotate and tap - so you can create Dynamic Actions on these events. As jQuery Mobile, the framework they're using, isn't production yet, probably some of these mobile features will be disabled in the first release of 4.1. 
Mike Hichwa had the keynote as the last session of the day. He outlined the plans for APEX after 4.1. Next on the wish list are more cool functions like a Modal Dialog, Multiple File Upload etc. It seems that every good plug-in out there will be added as standard functionality! Als providing RESTful web services will be a feature of an upcoming APEX release  - using the power of the APEX Listener.Talking about APEX Listener...some BI Publisher functionality might be incorporated in the AL, so the AL then can be used for generating PDF documents - a sort of "BI Publisher Light"...
Last but not least: Did you know Oracle uses an APEX application for their partner store and orders with a total worth of 4 billion dollar go through it....so, who dares to say APEX can't be used for business critical applications and is only suitable for small department level ones?

Comments

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…

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 …

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…