Skip to main content

APEX 5 New Static File Features

By
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 ...
Labels:

Comments

Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function
Post a Comment
Read more