Skip to Main Content

URL Columns

Apex View NameAscendingColumn Name
APEX_APPLICATIONSJAVASCRIPT_FILE_URLS
APEX_APPLICATION_PAGESCSS_FILE_URLS
APEX_APPLICATION_PAGESJAVASCRIPT_FILE_URLS
APEX_APPLICATION_TEMP_LISTCSS_FILE_URLS
APEX_APPLICATION_TEMP_LISTJAVASCRIPT_FILE_URLS
  • 1 - 5 of 22

Info

If you want to make sure that all Javascript and CSS files will be reloaded properly in the client browser when you deploy a new version of your Apex appliction, you can use the APP_VERSION substitution string.
The Oracle Apex documentation has some good info on this, and a very nice article on this subject named "Caching APEX static files" can be found at https://cloud.jaris.fi/ords/r/jaris/blog/post?p2_post_id=201803041325416124.

For example, you might include a CSS file using this URL:
/i/my-css/custom.css
Now if you were to upgrade your Apex application (and change its version number) and also make changes to the css file, the clients browser would not know about this and keep using the old version it has in its cache. So if you use this URL instead:
/i/my-css/custom.css?v=#APP_VERSION#
then Apex will substitute #APP_VERSION# with the version of your Apex application (e.g. 1.1), resulting in this URL:
/i/my-css/custom.css?v=1.1
Problem solved - the browser sees a new URL and will download it instead of using the cached version.

As you may have guessed, I needed to implement this for a number of Apex applications recently. The hard part turned out to be finding all the places where changes were needed. Once those (350+) changes were found, the rest was just a lot of repetitive work really :-)
I have gathered some code I wrote for this, that you may find useful:
  • View ted_p1146_url_columns_v (see the Report above): Find Apex views with JS and/or CSS URL columns. These indicate all the places in your Apex applications where URLs for external JS and CSS files are stored, and we need these to build the next view, ted_p1146_urls_in_apex_v.
  • View ted_p1146_urls_in_apex_v: Query all the places in your Apex applications where URLs for external JS and CSS files are stored.
  • View ted_p1146_urls_in_plsql_v: Query all the places in your PL/SQL code where URLs for external JS and CSS files are added using apex_css.add_file or apex_javascript.add_library. Strangely enough these procedures have no option to add this kind of version (p_version adds it to the filename, before the extension, so that doesn't help), so we have add it manually.

Code

Page

Name
Page ID
Name

Region

Identification
Sequence
Title
Type
Source
Source Type
Table Name

View

View
Name
DDL

View

View
Name
DDL

View

View
Name
DDL