Skip to main content

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 don't work as in a regular file system.
(Little side note here: Of course it is more convenient - and performant - to put those files on a web server and make the changes directly on the files. But alas, in some environments developers don't have access to the web server ....)

In APEX 5 .... this is all waaaay better and easier! First of all: There is no unnecessary distinction between file types. Just like pigs, all files are equal. There is only a logical distinction between Application and Workspace Files.
But wait. It gets even better. You don't have to upload all your files one-by-one anymore. You can just upload a zip file and upload that one. And the file will be unzipped into the different original files.
And if your zip file contains directories .... those directories are created in the APEX Repository as well. So now you CAN have relative references in your JavaScript files - as you can see in the screenshot below showing a set of uploaded Cordova files!  
And immediately you'll notice another handy addition: You can see how you can reference that file as well! And when you use a reference like #APP_IMAGES#database.png this will  be translated on runtime to something like roel/r/11788/files/static/v13/database.png. And that doesn't look like a procedure call anymore (wwv_flow_file_mgr.get_file....) but more like a path reference to a file.

And one more thing ....
You probably noticed the "v13" in the URL to that image. And this might be even the coolest part ... If you change a file and upload it with the same name - so no need to delete it first! - the reference will be automagically updated and points to your new file. Instead of "v13" it'll be using "v17" or similar. So you never experience caching issues as this is seen by the web server and your browser as a new file!

And as a bonus you can also select all the files from the APEX repository and download it as one zip file ...
Post a Comment

Popular posts from this blog

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 …

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…

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…