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

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 …

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…

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…