Skip to main content

#APEXinDublin

Last Tuesday CampusIT - in cooperation with Oracle - organized the first APEX event in Ireland. Around 50 people from around the country visited the O'Callaghan Alexander hotel for a series of five presentations around APEX (done by the four presenters on the picture). First on was Dimitri with his "Mastering an APEX Page" presentation - always a success. I was om next doing my "APEX and Forms Integration" presentation and demo.
After a - very good ! - lunch Bary McGillin from Oracle (from the SQL Developer Dev Team) was substituting Hilary Farell (from the APEX Dev Team), who couldn't make it - probably very busy with the last loose ends of APEX 4.0. After the APEX 4.0 presentation Barry did a presentation on SQL Developer 2.1.1.  But he also did a demo on the brand new 3.0 release. And as you might expect this release includes many new features and enhancements. Some of these features are aimed at the DBA, like changing Oracle parameters on the fly, adding datafiles and even starting and stopping instances. Other new things are more for Developers, like another way of browsing users and objects (more TOAD-style) and even a Tuning Advisor!
An early adopter of this new version should be available somewhere in the summer, while the official release is planned midst September (read "Oracle Open World"). All the usual disclaimers applied of course!
The slides of the presentations are available from the bottom of this page.
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…