Performance Improvements in SAP Hybris Cloud for Customer - 1705

[guru_shetti]

The following performance features and improvements are part of 1705.

 

1. Option to Disable Implicit Personalization to avoid cold starts

In 1705 we have introduced an option to disable implicit personalization. When this option is checked (turned on) as shown below, a user's specific layout changes will not be persisted. This means there is no need to get a copy of the users layout/floorplan from the server.

Usually this request to the server to get a copy of the users personalization takes somewhere between 0.5-2 seconds depending on the screen and the user's location. Please note that the request to retrieve the floorplan is one time performance hit for the particular user, until the next change is made via personalization or changes via the key user tool (KUT).

However, please note that since personalization changes are not persisted therefore next time the user visits the screen the changed layout will not be observed.

Lets walk through an example to discuss this feature assuming that the flag above has been turned on. The following screen shots will step through the explanation.

Step1: User navigates to list of accounts in the Customers work center

Step#2: User personalizes the screen to move the column Account ID next to the column Name

Step#3: When the user navigates away and comes back to this list, the layout changes revert back to the original layout. However since the floorplan was not retrieved from the server, there is no penalty incurred on performance.

2. Use of SAP UI5 1.44 libraries 

The SAP Hybris Cloud for Customer has been updated to UI5 libraries ver. 1.44. This version has inherent performance improvements for both Microsoft IE and Google Chrome browsers.

 

3. Improvement in User Experience and Performance with introduction of Page based scrolling (for Fiori Client)

In the Fiori client (formerly called as Responsive UI/RUI) we have introduced a page based scrolling as shown below. This is more efficient and also smoother in terms of user experience.



 

In 1702 we had scrolling that used to be triggered after reaching the end of the page. This is slightly interrupting in user experience and sometimes slow as well.

 

---