Skip to main content

ODTUG Kaleidoscope 2008 : The pre-conference conference


The day started with a rather fierce thunderstorm, and I can tell you that if it rains in New Orleans it really rains! This day was a sort of warming-up for the real conference with three full day symposiums on Essbase, APEX and Fusion. I attended the ‘The Seasoning of Application Express - Must hear Succes Stories‘ symposium that started off with an impressive presentation of Scott Spendolini. His theme was ‘Less is more‘, what didn’t refer this own presentation as he managed to go to 431 slides in half an hour! After that Mike Hichwa from Oracle did an ‘Apex Update’. He told us that currently APEX is the most used tool within Oracle for internal applications. Oracle also releases products that are based on APEX, like Database Vault. And we got a sneak preview of the future of APEX: we will get updateable interactive reports, custom item types, easy way to attach files of any kind to a record and declarative AJAX support. And some other good news: SQL Developer will support logical and physical data modeling - so we don’t need Designer for that anymore. And from these datamodels APEX applications can be generated using templates.

The other five presentations were user experiences. They all come together at one point: Application development can be incredibly fast when you use APEX, and that’s exactly what the business needs: short term to market and agile development. The IT departments have some difficulties in this paradigm shift: the regular long term waterfall approach doesn’t work here. And the risk is that the business users will develop the applications themselves (again, just like they did using Excel and Access), just because it is - or seems to be - so easy.

Just before the Welcome Reception Thomas Kyte did a presentation on ‘How do you know what you know…‘. It was the same message as he delivered 1,5 year ago during Open World, but with different examples: Knowledge is good, but can also be bad. If you had an experience in the past, that doesn’t automatically mean it still counts, because things, like the Oracle database, change. BTW it’s always a great pleasure to attend one of Thom’s presentations.
Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …