ODTUG: Thursday and the day after...

The last day of this great conference had "only" three presentation slots. The first one I attended, but honestly I didn't pay that much of an attention. I was writing my previous post at that time and I was rather familiar with the subject "Forms to APEX conversion". And I totally agree with the conclusions: Converting simple Forms is easy, but the more complex the Forms, the more work it will take to convert it to APEX!

The second one was called "APEX Stimulus Package". In fact it was more or less a list of things you have to consider to improve the performance of your APEX application - also due to the fact that most demo's didn't work because of a failing internet connection.

To name some of the tips: Reduce images sizes and use png instead of gif or jpg; check the Apache log for errors and resolve them; add a favicon.ico; watch out with pagination schemes; tune your Page 0 processes; use Page and Region caching where appropriate; minify javascipt and css files; externalize javascript and css files; refactor PL/SQL etc. Some of the tips where obvious, some of them quite useful.

The last one of this week was rather cool. Roy McLean showed how to use Oracle Data Mining in combination with APEX. I never used the Data Mining stuff before, and you might need a degree in maths to use it properly, but the things you can do are rather amazing. For instance you can predict what probably will happen. As an example Roy showed a sort of Helpdesk application where a call was assigned to a certain (pool of) engineers by the text that you entered when describing the problem!

After the show was over I paid a visit to Obama's house, the Washington Monument and checked out the West side of The Mall.
The day after. Friday, I had until 10PM before my flight was leaving, so I visited the Capitol and "did" the East side of The Mall. The weather was fine (cooler than at home!) and it was good fun.
As in previous years I liked ODTUG very much - the best conference in the world. Hope to be there again next year in Long Beach, California.

Comments

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 o...

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