Skip to main content

Handling a slow loading APEX Home Page - the easy way

Recently someone was asking me this question via e-mail:

"On my home page I have defined a couple of PL/SQL processes that take a long time - like 30 seconds - to finish. These processes fill up some collections that are used on the page to show information. But how can I let the user know that the system is "working", because right now they're watching at an empty screen (or the login screen) for 30 seconds."

Apart from speeding up the queries, there are two approaches to solve this (that I know off) :

The first one is using AJAX calls. So call the processes On Demand - using apex.server.process - and refresh the reports / regions when they're finished. Elegant, but it requires some recoding - and some JavaScript and that may not your first choice ...

An alternative is, to create a "page-in-between". So create a dummy page (like 999). Set the Home URL of the User Interface to that 999 (see pic below). So after login the user is send to that page.


On that page, create Dynamic Action that fires on Page Load, set the Action to "Submit" and in the Settings tab, set Show Processing to Yes - as shown below.


Subsequently, create a Branch to the (slow) Home page. Now, after login the user will see a "Processing bar" until the processes on the home page are finished and the page can be loaded.

For the most APEX Developers, the last alternative will be easier to implement than the one using AJAX calls ....

Post a Comment

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…