Skip to main content

OOW Suggest-a-Session : Top Voted Sessions

During the period the Suggest-a-Session for Oracle Open World 2011 on Oracle Mix is open, you can't see the rank of the (or your!) proposal. Only by accessing every proposal and writing down the number of votes, it is possible to get an idea of the rank of a proposed session. This is quite a cumbersome why not automate this? Heavily inspired by Wilfred van der Deijl, who wrote a Java program to do that, I created a similar functionality using just the Oracle Database. Who needs Java after all ;-)
The first set up requires setting the ACL right for using utl_http. Next I had to import the certificate Oracle is using for that site into the Oracle Wallet Manager and then create a function that retrieves all proposals and filters the title, presenter and the number of votes. This takes a while, so I dumped the results in a table. 
Next I uploaded the results to my workspace on (couldn't run the procedure from that site as the ACL there prevents the use of utl_http) and created a Report and a Chart on top of it. So now you can see your rank (I will - try to - update the data every day).

The link to the page is :
As you can see the session Marco and I proposed still needs some votes, so when you like this overview, please vote for our session as a "thank you": !

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