Custom Java Script Caching Issues Using Build Numbers

(Doc ID 2421558.1)

Last updated on JULY 13, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.20.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
--------------------
The build number in the URL remained the same before and after JS changes, i.e. the custom JS cache is not refreshed.

The screenshot with the build number appended for custom JS:

 

EXPECTED BEHAVIOR
-----------------------
Provision to change the build number and/or build ID whenever there is a change in the custom JS / CSS file.
The build ID is automatically added to the URL for custom files as well but not modifiable for custom builds.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.  Update a custom JS file.
2.  Deploy the Billing Care along with custom JS files.
3.  Open the page where the custom JS has impact.
4.  Verify whether the new JS cache is updated with the latest changes.


Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms