Configuring the Cache Buster for Custom Tile Types

If you have created custom tile types, you can add cache buster tokens to the URLs of your resources by creating a launchpad configuration file.

This is only necessary if your custom tile types are deployed to a location different from the standard SAPUI5 applications (^/sap/bc/ui5_ui5/(.*).chip.xml$) .

The following example shows how to add a cache buster token to the URL of a custom tile type:

{
    "description" : "This sample configuration is for adding cache-buster tokens as query parameter to Chip-XML files",

    "cacheBusting": {
        "patterns": {
            "^/<mycompany>/<mycomponent>/(.*).chip.xml$": {
                "replacement": "/<mycompany>/<mycomponent>/$1.chip.xml?sap-cache-id=[CacheBusterToken]",
                "order" : <99>
            }       
        }
    }
}

You need to adapt the path (/<mycompany>/<mycomponent>/) to the path where your CHIP definition XML is deployed.

The replacement parameter adds a cache buster token to the URL of your CHIP definition XML.

The order parameter allows you to specify in which order the system reads the configuration entries. The system reads configuration entries with the lowest numbers first, which means that the entries with the lowest numbers have the highest priority. The default configuration entries shipped by SAP have order number of 100 and above. This means that any numbers below 100 have a higher priority than the default configuration shipped by SAP.