Skip to Content
avatar image
Former Member

Cachebuster for Launchpad in Fiori Client


I've developed an SAPUI5 webapp, which I've also integrated into Fiori Launchpad. As I'm making use of the device's camera in my app I'm using the app in the native Fiori Client application of my OS.

I can use it standalone with the app's URL or with the Launchpad as starting point.

My problem is that in case I change anything in the program the change is not reflected in the app when starting it via Launchpad inside Fiori Client. If I start it standalone with the app's URL, after running /UI5/APP_INDEX_CALCULATE the new version of the program is called as the cachebuster is included in the bootstrap in index.html.

However, as the entry point in case of using the Launchpad is not the index.html, starting the program via Launchpad still starts the 'old' version of the program. Even if I clear all application settings in the Fiori Client, next time I start the program from Fiori Client via Launchpad, still nothing changes.

I've also invalidated the cache (e.g. with tr. SMICM, ...CACHE_CLEANUP) on the gateway, still without success.

I'm usin SICF service /sap/bc/ui2/flp/ to access the Launchpad, which if I understand correctly should already have cachebuster activated. In a webbrowser if I clear the history I'm getting the new version of the program, but not in Fiori Client.

Any ideas or suggestions how I could make my app get refreshed when running it inside Fiori Client via Launchpad would be highly appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 17, 2017 at 08:02 PM

    Refer to the link. Although it says cache buster, but the program needs to be run to activate new version.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you for your input.

      After doing the modification on the UI5 app, I'm running the report /UI5/APP_INDEX_CALCULATE for the particular app I've just changed, and when starting the app in Fiori Client with the app's direct URL (entry point index.html), the cache-busting mechanism seems to work, as the new version of the program is called.

      Though, if I'm calling the program via Launchpad URL (as a Launchpad tile) from Fiori Client, nothing changes, still the "old version" of the program is called.

      I've also noticed, that the iOS version of Fiori Client has a menu under settings to "clear cache", whereas the windows version doesn't have such an option.

      So I'm still wondering what needs to be done to make the new version of the UI5 app get fetched after a change if you run it from Fiori Client via Launchpad.