Skip to Content
Author's profile photo Manish Kumar

Performance Guidelines for embedding reports in the overview page

Performance Guidelines for embedding reports in the overview page:

In SAP Hybris Cloud for Customer, you have an option of embedding reports in the overview page.

Below screenshot provides the details of this feature on the Account, but this feature is available on other objects as well.

Fig 1.1

This feature enables to have a view of data at one place.

Few things need to be considered.

As this feature brings more data to be shown on the overview page, it impacts the performance of the load of the Account.

The End to End response time is directly proportional to the no. of reports embedded on the overview page.

Below example shows how exactly the performance is impacted:

In this case, only one report is embedded in the overview page of Account i.e. “Opportunity Analysis”.

Fig 1.2

If we check the HTTPWatch for the Account load, you can see more than one round trips, and the additional roundtrips happens asynchronously.

Note: From standard, the account load has only one round trip to server.

Fig 1.3

The additional roundtrips are for the embedded reports and this can be seen in the HTTPWatch trace.

The no. of roundtrips is directly related with the no. of embedded reports. Performance of each report depends on the amount of data displayed/queried.

With this a user can have an issue with performance.

Below section provides information on how this can be overcome during the load of the overview page.

When we embed the report via adaptation mode, we see an option called as “show collapsed view”, which is checked by default.

Fig 1.4

Once we uncheck this flag, the report tries to load asynchronously during the load of the overview page which inturn hits the performance.

But when we check this option, the report is collapsed by default.


Fig 1.5

With this approach, application doesn’t make extra round trip to the server to fetch the details by default.

Below HTTPWatch trace shows how the application reacts when the reports are collapsed.

Fig 1.6

When the user expands the report manually, that is when it makes a call to the server to fetch the details.

This approach enables a good user experience and enables them to get the details what they want to see.

With 1705 release, once the embedded reports are collapsed via adaptation in HTML5, you can see this reports collapsed in RUI (Responsive UI) as well.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.