Skip to main content

APEX 4.0 New Features

Image
By
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.

Comments

Stew said…
Sounds like pretty interesting stuff - especially the improved Tabular Forms (since they're used so much), Dynamic Actions and the WebSheets.

I hope they also work out the kinks in some of the existing minor features. For example, couldn't they come up with a better interface for editing Standard and Parent Tabs? I was working with them yesterday and it felt very cumbersome. :-(

Thanks for sharing this stuff.
3:06 pm
Roel said…
@Stew
I remember that at one of the sessions someone in the audience also complained about managing tabs. As I recall the development team was also looking into that.
3:30 pm
Anonymous said…
You said...

"an Oracle APEX Listener as a replacement for the MOD/PLSQL gateway;"

... what does this really mean? Any more details on this?
4:10 pm
Stew said…
Roel,

Thanks for the good news on that issue.
5:17 pm
Patrick Wolf said…
Roel,

my impression was that APEX 4.0 is not planned for "early 2009", it's more targeted for summer/fall.

BTW, was nice to meet you!
Patrick
10:42 pm
Roel said…
@Anonymous
Some more info on the Oracle APEX Listener you can find at the forum in this post : http://forums.oracle.com/forums/thread.jspa?messageID=2791285

@Patrick
Nice meeting again indeed! The "early 2009" is mentioned in one of the presentations of Oracle (with the regular disclaimers..). We'll see...
9:07 am
Stirl said…
Thanks that was very informative.

I cannot wait for jQuery and the jQuery calendars...
10:16 am
Drew said…
More important to me is the output/printing/export capability of the Interactive Reports. They are great but on the display, but horrible upon "download". That feature is supposed to be included in 4.0, export to Word, Excel, HTML, PDF, what is on screen, should be similar to the output.

Anyone know the date yet?
2:46 pm
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function
Post a Comment
Read more