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 exercise...so 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 apex.oracle.com (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 : http://apex.oracle.com/pls/apex/f?p=41715:80
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": https://mix.oracle.com/events/oow11/proposals/10930-xfiles-the-apex-4-version-the-truth-is-in-there !

Comments

Emre Baransel said…
That will absolutely make my life easier :)) Thanks a lot.
Kyle Hailey said…
awesome relief to a cumbersome interface - thanks !
Gave you guys a vote.
I hand made a list of presentations from Oracle Oaktable folks:
Oaktable sessions on Oracle Mix

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…

Adding items to your Interactive Grid Toolbar

The APEX Interactive Grid uses the Toolbar widget to create the default Toolbar showing the Search box, Actions menu, Save button etc. And since quite a while there is a nice Plugin "Extend IG Toolbar" by Marko Goricki that makes it very easy to add additional buttons to the Toolbar.

But what if you need more than a button? 
Inspecting the contents of widget.toolbar.js, you can easily spot there can be added more to the Toolbar than just a button: The type of control, available values:
"STATIC", "TEXT", "SELECT", "BUTTON", "MENU", "RADIO_GROUP", "TOGGLE".
The first example will show a way to easily switch from one filter to another. Of course we could use the standard functionality and create two different Report views, but using a Radio Group on the Toolbar gives a more "Tab" like user experience.

So how can we create a Radio Group that looks like a switch in the Toolbar?
In the Javascript Code …

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…