Skip to main content

Some "small" APEX 4.0 EA3 features...

In the latest release of APEX 4.0 (available on tryapexnow) I noticed two nice new features. First of all, on the far right side of the Home page of the builder, there is a little region called "Available Updates". If you click on the little "i" in the upper right of that region, you'll navigate to another page where you can control if you want to check for those updates. Wonder what will happen if I set it to "No"...will it be switched of for just my workspace or for the whole APEX instance? To me it seems it should be an "Administration" kind of functionality - so instance wide. In the "Help" it says: "This attribute controls if Application Express should check if updates are available for Oracle Application Express and the Oracle Application Express Listener. Note: To perform this check Application Express transmits the version number of Application Express and other system components to Oracle Corporation." This seems like a nice functionality to get a sort of alert if there is a patch available. I don't know if you need a Metalink account to enable this feature.
The second one is a "Set Screen Reader Mode On" link at the bottom. If you click that a SET_SESSION_SCREEN_READER_ON is added to the URL of the Builder. I assume that this means that all HTML rendered can be read by a screen reader like JAWS to enhance the accessibility of APEX for visually impaired developers.
I inspected the HTML source of that page before and after that setting and it seems that nothing has changed. Maybe because all rendered HTML is already "screen reader ready"?
Next to these things there are a lot of new features in APEX 4.0. Check out the New Features Application to see a dozen of nice examples. Also check out the Learn More About Oracle Application Express application - which seems a Websheets application to me....
3 comments

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…