Skip to main content

APEX 4.0 New Features

At OOW some new features of the upcoming major release of APEX, version 4.0, were revealed - ofcourse with all the regular disclamers applied. Here a (non complete) list of the announced features - in a random order:
  1. The option to use an Application Timestamp Format, next to the existing Application Date Format;
  2. The option to use the Client Time Zone;
  3. jQuery will be included in the APEX distribution;
  4. instead of the (horrible) HTML-calendars, the much better looking jQuery Calendar will be used;
  5. the jQuery Calendar will offer an Extensible Item Framework, to create your own calendar types;
  6. ofcourse the famous Websheets;
  7. an Oracle APEX Listener as a replacement for the MOD/PLSQL gateway;
  8. Improved Tabular Forms, thus reducing the need to build these manually;
  9. more JSON;
  10. Dynamic Recreation of Select List (from JSON), used - o.a. - for cascading LOV's;
  11. Namespaced apex.*.*, to reduce the risk of confusing variables in Javascript;
  12. Chainability;
  13. and last, but certainly not least, Dynamic Actions.
At the demo booth I saw a demonstration of these Dynamic Actions: a declarative way to define show/hide and enable/disable of items - depending on other items values. The goal is to reduce the manual Javascript coding. This was just a first example and more functions will be added in the final version. Also the option to create a Dynamic Action for a validation (e.g. P3_ORDER_DATE is not null) will be available in the future!

Reading this everbody screams : I want it and I want it now! But you have to be patient. The 4.0 release is aimed at "early 2009". First we should get our hands on the 3.2 release (this year), supporting the Forms2Apex migration.
8 comments

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…