Skip to main content

ODTUG Kaleidoscope 2008 : APEX rules!

In a couple of weeks ODTUG's Kaleidscope 2008 takes off. This years theme seems to be: APEX, APEX and again..APEX. At least, for me it is. Because my preliminary schedule is packed with 24(!) APEX sessions in 5 days. So at Thursday afternoon I should know everything I always wanted to know about APEX, but were afraid to ask.
I'm looking forward visiting New Orleans and meet again some friends from the Oracle blogosphere. I will report back my findings here!

So here's the schedule:

































DateFrom To Title Presenter
Sunday 9:00 10:00 Managing the Army's Enterprise Real Property Planning with Oracle APEX Bharat Pappu and Brian Duffy

10:00 11:00 Creating Dynamite Applications that Deliver Kathy Hunsicker

11:15 12:15 Oracle Application Express: Power to the People Rich Mutell, Dimitri Gielis, John Scott

13:00 14:00 How IntelliReal used Oracle Application Express to Rapidly Build their Production Environment Chris Ostrowski

14:00 15:00 Mastering Unreasonable Deadlines with APEX at the German Telecom Shops Dietmar Aust

15:15 16:15 How Iron Mountain Has Used APEX to Improve Operational Abilities Within the Enterprise Chris Veenstra

16:15 17:15 APEX Roundtable With Panel of Presenters Moderated by Scott Spendolini

18:00 19:30 Welcome Reception and Jam Session
Monday 10:30 12:00 APEX Hints, Tips, and Best Practices John Scott

13:15 14:15 The Top 10 - No 11 - New Features of Oracle Database 11g Tom Kyte

14:30 15:30 Forms Migration to Java ADF Rohit Bhalla

16:00 17:00 Use the Power of APEX Dictionary Views to Increase the Quality of Your APEX Applications Karen Van Hellemont

17:15 18:15 Oracle Application Express (APEX) Version 3.1 David Peake
Tuesday 8:00 9:00 APEX Development: Watch It Live Bill Holtzman

9:15 10:15 You Can't Do THAT in a Browser! Extending Oracle APEX with Third Party Components Scott Spendolini

10:30 11:30 Advanced Oracle Application Express Tips and Techniques Chris Ostrowski

12:45 13:45 APEX Experts Panel (SIG) Scott Spendolini

14:00 15:00 Application Express in Support of Institutional Strategic Planning Tanya Podchiyska

15:15 16:45 Writing a Custom Authentication Scheme for Application Express: A Case Study Raj Mattamal

17:00 18:00 Explore and Benefit the APEX Repository Michiel Jonkers

18:00 19:30 Meet the Oracle Ace Directors and Oracle Aces Reception
Wednesday 8:00 9:00 Creating Dynamite Applications in Application Express that Deliver Kathy Hunsicker

9:15 10:15 Building Advanced Tabular Forms Marcie Young

10:30 11:30 Creating Advanced Charts in Oracle Application Express Dimitri Gielis

13:30 14:30 Increase Your Oracle APEX Development Productivity with Open Source Tools Patrick Wolf

14:45 15:45 How to Hack an Oracle Application Express Application Anton Nielsen

16:00 17:00 Building the New Stuff: AJAX, JSON, and APEX 3.1 Carl Backstrom

18:30 21:30 New Orleans Party
Thursday 8:30 12:00 APEX Versus ADF Lucas Jellema, Dimitri Gielis

Comments

Popular posts from this blog

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

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

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