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!
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…