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!

Comments

Learco Brizzi said…
Sounds like a nice day. I'll hope APEX will be as popular in Sweden as it is here in Holland :-)
sLars said…
It is starting to evolve. I do not fully understand why there is such hesitation.

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…