Skip to main content

OGH APEX Day 2011

Yesterday it the Dutch Oracle User Group (OGH) organized a full day APEX-only event. And what a day it was! With 250 attendees it was completely sold out. And I guess, if there had been more room, there might have been even close to 300 people there. So APEX gaines more and more interest - and faster and faster... 
And where did all those people came for?

Before lunch there were three general sessions. The first was by Tony Andrews and Nigel Blair of Northgate, talking about their 1500 Forms-to-APEX conversion project. They succeeded and therewith proved (again) that APEX is capable of running enterprise / large scale / mission critical applications. But as they started some years ago, they couldn't use all the new cool stuff, like Dynamic Actions, and therefor build an own framework. And that might require "some" work to bring it into the APEX 4 world. But that's the disadvantage of being ahead of the curve!

Then Hilary went on stage to tell - and show! - us the new APEX 4.1 stuff. There is a list of the things you might expect for 4.1 (see Statement of Direction), but to actually see (some of) it is always better. The new Themes/Templates using jQuery Mobile delivers an awesome result on a smart phone. Another good thing is that 4.1 will support not only Static Lists - as we know nowadays - but also Dynamic Lists! So it will be a lot easier to generate your menu's etc from a database table.
The validations and processes for Tabular Forms are improved. For instance, you can define validations for each row or once per page - using SQL or PL/SQL. And you can also trigger these validations for only updated and new rows or for all rows.
Also the Dynamic Actions are enhanced: you can use conditions within Dynamic Actions, so you don't need to create multiple similar ones.
The  number of Plug-in attributes will be raised up to 15 (still not enough, according to some). But even better, there will be new types of Plug-ins: for items in a tabular form, for Authentication and Authorization Schemes. Regarding the regular Forms: The use of ROWID will be supported and also using primary keys with more than 2 columns isn't a problem anymore. 
Also Websheets are revamped. The look-and-feel and navigation is improved. A thing that came rather strange to me is that sections within a page can also be based upon PL/SQL. And I thought that Websheets was aimed at the (experienced) end-user. But my end-users don't write PL/SQL code. Not even the experienced ones. I hope...
And of course someone asked the usual question - and the answer was "Calendar year 2011". (All things said/shown with the usual Oracle disclaimer).

Next John and Dimitri shared the stage. Doing a presentation (or an act?) about their newest idea: FoogleTwit. Within a few years, "The Social Network, part 2" will shine a light on this!  But it seems, that that name is first mentioned in a comment on a blogpost on Feb 10 this year. So there might be some law suits coming up...
The content was great though: They showed how APEX Evangelists run their projects.

After lunch there were three parallel tracks: Core APEX, APEX and ?, APEX at Work. The first one I attended was by Peter Raganitsch about the Translation Mechanism. In short: it works, but takes a lot of work and maintenance is not so simple. So if you can stay away from multi-lingual applications, you should. Otherwise, the best tip: Do your translations as far in the end as possible. So after running in production for a fair amount of time (so most bugs will be fixed by then).

Then it was my turn. I presented about "Charts and Dashboards". I showed a lot of Charts: First the regular once, then the slightly adjusted one and the completely revamped one. Some of the charts and dashboards demoed might require an additional Anycharts license (as Hilary pointed out). This was my first presentation where the demo and the presentation were tightly integrated: it was one and the same APEX application. You can see it here : You can click through the "slides" using the Next and Previous buttons at the bottom. And open up the Hide/Show regions where ever they pop up. Only the part that uses the APEX Listener Templates won't work...

The last presentation I attended was Dimitri's one about APEX and Locator / Spatial. The solution and demo he did was very impressive. This spatial stuff is even more powerful than I thought. But not so easy to comprehend though... It will take some time to get to know this stuff.

They day was concluded with some drinks and a nice dinner. It was a long day, but worth every minute! And, of course, a special thanks to the organizing committee. They did a hard job very well! 

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…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…