Skip to main content

#APEXinAntwerp - The first OBUG APEX SIG

Last Thursday the first official OBUG (Oracle Benelux User Group) was held in Antwerp with APEX 4.0 as the main subject of all presentations. Over 80 attendees attended this event and listened to six presentations during the day. Although it was very warm (some people would claim even 'hot') in the room, (almost) nobody feel asleep - for long.
After a warm welcome by Dimitri, Patrick Wolf showed a lot of the cool new APEX 4.0 features in a 1,5 hour presentation and demo. 
Next another Patrick (Hellemans) from InterAccess did a presentation on The Maturity Level of APEX.  According to Gartner and Forrester APEX will kick off (even more) the next two years! He also demo'ed an APEX Framework they made, to enable a kick start for APEX Application Development. Looked very good!
After a lunch with some nice sandwiches, I did my first gig on "Developing a Google Visualization Plugin for APEX 4.0" - the same as I will do next week at ODTUG. I think it went pretty well for a first time - the timing was exactly one hour ! - but I will make some minor adjustments for the next run. 
Next Dimitri was on with a nice presentation about Websheets and Team Development. He especially showed how easy it is to incorporate feedback in your application and transform feedback into bugs or enhancement requests. Will really change the way we'll develop and maintain APEX applications!
Olivier Dupont and Jan Huyzentruyt of iAdvise showed a lot of new 4.0 features that are not as eye-cathing as the Websheets, Team Development, Plug Ins etc, but will have a major impact on the speed of development and the quality of the work we'll deliver. Especially the comparison between the 'old' and the 'new' way of working was very interesting.
Last but not least was Iloon Ellen from Oracle, who focused on the enhancements made in the Tabular Forms. In the 'old' - or 'current' - version, Tabular Forms are always cumbersome. But the APEX Dev Team made some great enhancements to it, so handcrafted Tabular Forms (using apex_item) will not be necessary as often as they do now! Great stuff.
After the show was closed, Dimitri, Iloon, Learco and myself had a nice dinner on one of many outside terraces in Antwerp. It was a long (from 6AM to 11PM), hot and tiresome day, but definitely worthwhile!
The next APEX OBUG SIG will be .... on October 27 and 28 in Brussels. In conjunction with ODTUG's OPP and APEXposed. That definitely will be an event not-to-miss, so block these dates in your agenda!
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. …