Skip to main content

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 Javascript is easy, with Oracle JET”. I do like JET, but I am not sure all attendees shared Geertjan’s view. They probably were more convinced that APEX is way easier than JET....

Next on stage, the last before lunch, was Alex Nuijten talking about "JET Charts in the world of APEX”. It was a very nice intro into the world of JET charts and Alex showed some peculiarities you have to be aware of. For instance, if you have multiple series, make sure all your queries return the same number of rows and in the same order. Or - as Alex is promoting - release your inner SQL Ninja and use the SQL power to get a proper result in one pass!

After a very good lunch (the quality of the food and drinks was a lot better than I have seen at other conferences, kudos for the organisation!), it was time for my first session, "A Deep Dive into APEX JET Charts”. In this session I am trying to convince the audience that looking into the JET documentation is really worthwhile: with just one or two  lines of JavaScript you can add a whole new user experience layer to your pages: much more interactive and dynamic! And for the JET components that are currently not exposed in the APEX Builder, you can create a plugin. Not that hard either, a few lines of PL/SQL, a couple lines of JavaScript and a SQL statement can do the trick! I hoped people liked it. I did get very positive feedback of Geertjan, who is the Product Manager of JET, that he didn’t know it was that easy to modify or incorporate JET Charts in APEX! 


After my session I went to one of the other rooms 4 decks lower to listen to Matt Nolan. He was "Unlocking the power of the APEX plugin architecture”. Compared to previous performances Matt did an excellent job! I don’t know if the attendees will start developing plugins en masse, but it didn’t look too complicated (to me)!


The last keynote of the day was another JET Charts session, "Advanced Charts in APEX 5.1 and beyond” by Hilary Farrell. Inevitably there was some overlap with Alex’ and my session, but also enough new stuff (and around ⅔ of the attendees probably had missed those sessions anyway). Hilary showed some cool examples how to chance the look of the chart or add functionality by just a few lines of Javascript. And in APEX 5.2 … we will get upgraded jQuery (3.x) and jQuery UI (1.12.x) libraries and the latest and greatest version of JET (probably 3.x).

Because a presentation of Uber was cancelled there was an "Ask the experts panel” added to the agenda. Three of the seven experts are member of the SMART4Apex co√∂peration, but to be honest, most questions were addressed to and answered by Mike. As SMART4Apex we delivered seven (7!) presentations, enough to fill one of the three tracks for both days...


After this extra session, it was time for drinks and dinner. And because the weather was absolutely fabulous, we could enjoy it all on deck while watching the sun set over Rotterdam.
A great end of a fantastic first day!

Post a Comment

Popular posts from this blog

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…

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…

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 …