Skip to main content

ORCAN event

Yesterday I attended an event organised by the Swedish Oracle User Group (ORCAN). They picked a real nice venue for this meeting: the top floor (54) of the Turning Torso. From this top floor you have a stunning view over the Oresund (all the way to Copenhagen) and Malmö and it's surroundings. Might be a little bit distracting from the presentations, but nevertheless...
There were two concurrent presentations. The first one I attended was by Moren Egan about Edition Based Redefinitions. As I presented about the same subject at OOW and UKOUG, I was just curious about how he would present this material. More SQL*Plus oriented as I did it, but I think the message came across just fine. The second one was by Randolf Geist, called "Advanced Oracle Troubleshooting". In fact it was just the first half (the second half was after lunch). Although I could grasp most of he said, some details were a little bit over my head. So I skipped the second part and went to SQL Developer New Features by Sue Harper. I was already familiar with most of the features, but it's still worthwhile to renew your insight about this product. It is growing with every release!
Then it was my turn wih APEX 4 New Features. To my surprise 75% of the audience had no experience at all with APEX - so all features are new to them! But I emphasized and spent most of the time demoing the cool Dynamic Actions and Plug-ins. Just to show how you can create stunning results with almost no coding! After a short coffee break I presented about Charts & Dashboards. This time I had alomst all attendees in my class, as the "other side" only had 4 (sorry Sten). All went pretty well I think, but I have to admit, doing two presentations back to back is a little bit exhausting.
Then it was time to leave for dinner in the center of Malmö. When I got my jacket I noticed my pockets were empty - and I was pretty sure I left my car keys and phone in there (which isn't that smart, I have to admit)! So a little panic broke out. We contacted the reception, searched the whole place - but nothing found. But then I noticed that there was something else missing from my jacket: It had just the Oracle logo, and mine had Oracle ACE Director logo! So it wasn't mine! A quick thought whose jacket it could be...and it had to be Sten Vesterli. And Sten was on his way to Copenhagen... We phoned him, but got his voice mail. So we went to the restaurant...and there was Sten with my jacket. While walking to the station he noticed there was a phone in his jacket (or my jacket) and another one in his pocket. So he also concluded he had taken the wrong one - and decided to go to the restaurant to exchange jackets. A total relief for me. Thanks Sten - not for taking the wrong jacket, but for returning it ;-) !
We had a nice dinner outside on the square. This little square is packed with restaurants and everyone is sitting outside. So they have a lot of heaters (and I mean really a lot!) and blankets for everyone. So I think global heating is for a major part caused by the Swedish... ;-)
All in all a nice event and I am looking forward to the next one!

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