Skip to main content

#APEXinAntwerp - The first OBUG APEX SIG

Last Thursday the first official OBUG (Oracle Benelux User Group) was held in Antwerp with APEX 4.0 as the main subject of all presentations. Over 80 attendees attended this event and listened to six presentations during the day. Although it was very warm (some people would claim even 'hot') in the room, (almost) nobody feel asleep - for long.
After a warm welcome by Dimitri, Patrick Wolf showed a lot of the cool new APEX 4.0 features in a 1,5 hour presentation and demo. 
Next another Patrick (Hellemans) from InterAccess did a presentation on The Maturity Level of APEX.  According to Gartner and Forrester APEX will kick off (even more) the next two years! He also demo'ed an APEX Framework they made, to enable a kick start for APEX Application Development. Looked very good!
After a lunch with some nice sandwiches, I did my first gig on "Developing a Google Visualization Plugin for APEX 4.0" - the same as I will do next week at ODTUG. I think it went pretty well for a first time - the timing was exactly one hour ! - but I will make some minor adjustments for the next run. 
Next Dimitri was on with a nice presentation about Websheets and Team Development. He especially showed how easy it is to incorporate feedback in your application and transform feedback into bugs or enhancement requests. Will really change the way we'll develop and maintain APEX applications!
Olivier Dupont and Jan Huyzentruyt of iAdvise showed a lot of new 4.0 features that are not as eye-cathing as the Websheets, Team Development, Plug Ins etc, but will have a major impact on the speed of development and the quality of the work we'll deliver. Especially the comparison between the 'old' and the 'new' way of working was very interesting.
Last but not least was Iloon Ellen from Oracle, who focused on the enhancements made in the Tabular Forms. In the 'old' - or 'current' - version, Tabular Forms are always cumbersome. But the APEX Dev Team made some great enhancements to it, so handcrafted Tabular Forms (using apex_item) will not be necessary as often as they do now! Great stuff.
After the show was closed, Dimitri, Iloon, Learco and myself had a nice dinner on one of many outside terraces in Antwerp. It was a long (from 6AM to 11PM), hot and tiresome day, but definitely worthwhile!
The next APEX OBUG SIG will be .... on October 27 and 28 in Brussels. In conjunction with ODTUG's OPP and APEXposed. That definitely will be an event not-to-miss, so block these dates in your agenda!


Popular posts from this blog

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…

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…

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 …