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…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …