Client-Side Caching of Target Mappings

Target mappings are stored in the client cache.

When navigating between applications or when filtering tiles according to the device types on the home page, the client cache stores the resources that are retrieved from it when the user requests them again.

The target mappings are user-specific and are based on the roles assigned to the user in PFCG.

Data remains in the browser cache until it is deleted by the user or cleaned up by the browser when its expiry date is reached. To avoid data caching, use the private or incognito browsing mode.

Cache Buster for Target Mappings

A cache buster token for target mappings is used to make sure that data is read from the server rather than from the client when settings for target mappings were changed. Parameter sap-cache-id is added to the URL to store the cache buster token.

A new cache buster token for target mappings is calculated if one of the following changes:

• Target mapping configurations in the launchpad designer or in the Launchpad Customizing (transaction LPD_CUST) if the role of the user sending the request is assigned the catalog which comprises the changed target mapping.

• SAPUI5 application components

• Settings in the Configuration of RFC Connections (transaction SM59)

• System alias mappings in table /UI2/SYSALIASMAP

If one of these settings changes, the client-side cache is invalidated and the target mapping is read from the front-end server. Otherwise, the target mapping request is read from the client cache, which significantly improves the performance.

Changes to Launchpad Customizing (transaction LPD_CUST) affecting a user’s target mappings not only result in the generation of a new cache buster token (leading to a client-side cache invalidation) but also in the invalidation of server-side cache.

Note To make sure the cache busting mechanism works correctly for target mappings defined in Launchpad Customizing (transaction LPD_CUST) we recommend you implement SAP Note 2243928 .

If you do not implement this note, changes in the Launchpad Customizing may not be reflected in the launchpad. To fix this inconsistency, you need to manually invalidate the cache using report /UI2/DELETE_CACHE.