SAP Screen Personas: where is tab caching in version 3?
Combining information from multiple tabs is one common way customers improve usability with SAP Screen Personas. This eliminates keystrokes and allows organizations to present information in a more intuitive way. In SAP Screen Personas 2.0, we accomplished this by caching all the content in each tab that contained information that you wanted to display. In SAP Screen Personas 3.0, we use a different approach – without caching.
In SAP Screen Personas 2.0, we gave developers the ability to use tab caching to pre-load and pre-fetch data from the backend. This means that if five tabs are cached, the information of all five tabs is retrieved from the backend and stored in the browser. The content within the tabs has a significant impact on performance. A tab with a few information fields will probably not cause performance problems. A tab that contains a large table – such as those common in sales order or material master transactions – is more likely to slow performance if you cache it.
In SAP Screen Personas 3.0, we changed the underlying architecture so that tab caching is no longer necessary. Tabs are now merged so you can display information from multiple tabs on a single screen as before, but without caching. You define the information you want on the screen, the backend stores the field codes, and renders them at runtime using the incremental loading that is already part of the Web GUI (SAP GUI for HTML).
As we learned from SAP Screen Personas 2.0 extensive tab caching can cause performance issues, so we no longer allow the pre-loading and pre-fetching of data from the backend in SAP Screen Personas 3.0. This proves to be much more effective with fewer calls to the backend and much less data transfer. Overall, this new approach has a positive influence on the performance when merging tabs.
The complimentary openSAP class starting March 31st (https://open.sap.com/courses/sps1) will also include a section on tab merging which will demonstrate how you can quantify the expected performance impact result from the use of tab merging in SAP Screen Personas 3.0.