APEX 4.0 : Overwhelming...

Just like the rest of the 'APEX World' I immediately jumped on the 4.0-bandwagon and signed up for a workspace on http://tryapexnow.com. Although I have seen a lot of the 4.0 stuff this year, but having the thing in your own hands is something completely different! IMHO this version (even without Websheets!) is the major APEX release ever. There are so many new, enhanced or restyled features, it just blows you away on first sight. I almost feel a newbie again...
I hope to find the time to dive into some new features the next couple of days (or probably weeks..).

Comments

JohnA said…

oh god.. Is this going to be like microsoft now, where we have a major release every few years, and we have to relearn EVERYTHING from scratch?

Guess it's time to start looking at Apex alternatives..

5:15 pm

Anonymous said…

JohnA,

The sky is NOT falling. While there are a ton of new features in APEX, and a new tree view for page edits, everything else is still very familiar. You can even switch back to the "Component View" if you like.

It's like buying a newer version of your current car and adding a few more options. Sure, it may be a different color and there are more buttons, but the steering wheel, gas, break, and gearshift are all still in the same place. You might have to read the manual for the new navigation system, but what do you expect, you didn't have a nav system before.

Tyler

9:32 pm

JohnA said…

Whew.. Thanks Tyler, that sounds much better. When Roel said "overwhelming", it brought back bad memories of the constant pointless paradigm shifts involved with Microsoft application programming.

11:07 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