Skip to main content

OOW2008 - Sunday

Image
By
Due to the jet lag this Sunday had a very early start. I was wide awake at 5:oo AM, so I had a long time to check my e-mail, take a shower and eat a full American breakfast. After registering for the conference it took about 5 minutes to walk into someone I know...it's a small world after all.
For me the conference started with a Hands-on-Lab : Extending the APEX Framework with Web 2.0. To me there where just a few new features mentioned in the handbook, but I guess most people didn't finish all examples within an hour. The handbook will be available as an OBE within a couple of weeks. The next session was on Achieving ROI with Oracle Database 11g and APEX. It was about a new application Harvard Pilgrim needed to offer health insurance to individuals. Instead of taking 1000's of phone calls, they decided they needed an on line self service application - and built it in APEX. Another good example how you can build an application with APEX in less than a month. You can find the application here.
After that Joel Kallman presented on Globalization with APEX. Apart from Java (with resource bundles) and .Net (using resource files), in APEX you can do the translation after the development. It needs just 6 easy steps: Map, Seed, Export (to XLIFF), Translate, Import/Apply and Publish. The translated versions of an application are replica's from the original one (with their own application id). You can only make changes to the original application. After changes you just have to make the additional translations and (re)publish the translated one. Live has never been so easy. One free tip from Joel : Create your database using the AL32UTF8 character set, so you can easily handle all languages... Examples of multi language APEX applications are BioQuebec and ProMed. He also announced some new APEX 4.0 features, but I will collect all those features for a separate post.
After the session about Weird PL/SQL by Steven Feuerstein and the - funny political - keynote by Carville and Matalin I went to the Blogger meetup. Allways good to match names and faces...
Labels:

Comments

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