caching-the-last-executed-request-4215eca.md

Caching the Last Executed Request

You can enable the catching of the last executed request on the list report page.

Note:

This topic is only applicable to apps using SAP Fiori elements for OData V4 in SAP S/4HANA Cloud Public Edition.

When the list report page is configured to load data automatically, the last executed request is stored on the client to improve performance. Caching applies to the request parameters, not the response from the back end. Storing the last executed request enables triggering the request while the application loads. This approach reduces the end-to-end response time.

Request caching is disabled if any of the following conditions are met:

• The request contains a filter on properties that are annotated with PersonalData.IsPotentiallySensitive. For more security-related information, see Security Configuration.

• A controller extension is defined on the list report page. Request caching is disabled in this case because the request can be modified through extension points on the list report page to add filters on sensitive data. If such filters are not added, you can still enable request caching by using the disableRequestCache parameter as shown in the following sample code:

  Sample Code:

  manifest.json

  "routing": {
      "targets": {
          "RootEntityList": {
              "type": "Component",
              "name": "sap.fe.templates.ListReport",
              "id": "RootEntityList",
              "options": {
                  "settings": {
                      "entitySet": "RootEntity",
                      "controlConfiguration": {
                          "@com.sap.vocabularies.UI.v1.LineItem": {
                              "tableSettings": {
                                  "disableRequestCache": false
                              }
                          }
                      }
                  }
              }
          }
      }
  }
  

  Note:

  When using the disableRequestCache parameter, ensure that you're not adding any filters on sensitive data.

Users can control cache expiration and clear the cache in the SAP Fiori launchpad settings.