Skip to main content

OBUG APEX SIG 2011

The OBUG APEX SIG, held yesterday in Vilvoorde (near Brussels), was a smashing success. Due to the overwhelming amount of registrations, we even had to disappoint some people... Next year we should look for a venue that can accommodate more people!
Due to a long (at least, longer than I expected) driving time, I arrived during Anthony Rayner's presentation on APEX 4.1. It contained lots of demo's, especially the ones about the new error handling features where impressive: this is really a major improvement! The remarkable thing about the presentation itself was, he used a new feature of Websheets: Presentation Mode! Using this, you can (more or less easily) create presentations that contain real live data!
After the coffee break, iAdvise did a nice presentation on how to build (and use) Plug-ins. It was a smooth step-by-step approach on how to create a Plug-in. Well done guys!
The lunch was excellent, thanks to Oracle...

Right after that, John Scott did a presentation on OHS, EPG and APEX Listener. Too bad he ran a little out of time, so he couldn't address all the cool features of the AL. Nevertheless a very useful presentation when you have to decide which web server method you need - or better stated : when to use which one...because "it all depends" of course...
The next track I skipped to run through my own presentation once more - because it was the first time I would be doing "Done in 60 seconds - Creating Web 2.0 applications made easy". The presentation is all about the coolest feature (according to the OTN Forum poll) of APEX 4.0 : Dynamic Actions. I managed to do all demo's without any (major) flaw, so I think it all went pretty well....
Before the long trip home, I had some drinks and chats with the other attendees. It was good to see all those familiar (and new!) faces again.
Thanks to Oracle for hosting this event! But next time we should look for a venue somewhere in (the south of) The Netherlands...
Post a Comment

Popular posts from this blog

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…