Rumors about APEX 4.0 release date on OGh APEX Day

Yesterday the OGh (Dutch Oracle User Group) organized a full day about APEX. There was a very good turn-up of about 150 attendees and about 10 sessions to choose from.
A couple of attendees already blogged about it like Rob, Michel and Dimitri. I agree what they already have written so I won't repeat it.

There also was a rumor - that I heard of before, so it might be true - that APEX 4.0 is planned to be released just before/after or even during ODTUG... So around the end of June we will experience if the source of the rumor is a reliable source or not...

Comments

Patrick Wolf said…

Rumors, rumors, rumors... :-)

1:38 pm

Pat Miller said…

Are any html 5 features being built in to Apex 4?

Pat Miller

3:10 pm

Patrick Wolf said…

Hi Pat,

what HTML 5 feature would you like to see.

Regards
Patrick

11:02 am

Pat Miller said…

Some of the features I have read about like:
Vector graphics -- svg enhanced
Web workers --background processing of more complex scripts
Embedded videos

Pat

4:31 pm

Unknown said…

I think the more useful features of HTML 5 for APEX are multiple file upload and local storage, perhaps to cache navigation elements and lists of values. I agree that web workers would be useful as the ajax events get more complex. APEX doesn't really need to do anything to support video in HTML 5.

Tyler

4:14 pm

Filtering in the APEX Interactive Grid

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

apex_application.g_f0x array processing in Oracle 12

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

Stop using validations for checking constraints !

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

Roels Blog

Search This Blog