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

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…

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…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …