on ‎2023 Jul 24 5:35 PM
Hi,
I have added an HTML Viewer using SAP Personas to trasnaction PFCG. The HTML Viewer has a link to transaction KSH3 and the purpose of this is to allow users to easily view cost centre data when choosing roles:

The problem is that whenever the user performs an action on the PFCG screen, the HTML Viewer always refreshes, causing the user to lose any information they had entered. For example, if the user is searching for roles, the HTML Viewer starts to refresh, and the entered data is lost:

Is there any way to prevent the refreshing, when the user performs an action in PFCG, and so retain the user-entered data in the HTML Viewer?
Thanks in advance!
Request clarification before answering.
Are you owning the code where the HTML viewer is used? If so, you shouldn't create a new instance of the HTML control in GUI each roundtrip. Instead the instance of the Cl_GUI_HTML_VIEWER should be a global variable in the program and only be instantiated at the very beginning.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, this question has remained unanswered so far, which is regrettable. Does SAP not have a solution? My impression, however, is that it is fundamentally not possible to use dynamic web pages within SAP Personas. This is because the transaction displayed in the browser, which might have an embedded WebView, is reloaded upon executing a script. SAP Personas would need to somehow cache this view or keep it available elsewhere, which is probably not feasible in this architecture. However, I am open to being corrected and am very interested in a solution.
My use case is as follows: I had the idea to integrate additional components, for example, a React application, within SAP Personas. Or other dynamic pages as well. But if a reload occurs as soon as an SAP Personas script is invoked, this seems fundamentally impossible, which would be very unfortunate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Robert, could you please provide more details on this. From what we can observe in screenshots, it looks like it is working as designed and there are technical reasons for that. Maybe you can describe what are you trying to achieve and we can propose better solution for you.
Best regards
Artemijs, Screen Personas development team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Artemjis,
Thank you for getting in touch. I appreciate your help.
Let me explain the scenario we have developed:
-Users frequently need to assign roles using the PFCG transaction.
-Sometimes, before they can determine the correct role, they have to look up cost center hierarchies in transaction KSH3. In KSH3, they have to navigate through multiple screens to reach the cost center entry screen.
-To streamline this process, we have created a custom flavor for KSH3 that automates all the steps required to reach the cost center entry screen. This flavor is then called via an HTML viewer embedded within the PFCG transaction. The purpose of this integration is to allow users to access KSH3 and determine the cost center hierarchy without leaving the PFCG transaction.
-However, the issue we are facing is that after users determine the cost center hierarchy using the HTML viewer, any attempt to use PFCG functionality (such as looking up a relevant role) causes the HTML viewer to refresh, resulting in the loss of the information they found.
We are looking for a solution to prevent this continuous refreshing of the HTML viewer and retain the information found by the users.
Thanks in advance.
| User | Count |
|---|---|
| 8 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.