Posted: 5 Aug 2019 9:53 EDT Last activity: 9 Aug 2019 5:49 EDT
Case Creation and data spreading
Hello dear community,
I have some troubles with some native Data Page and data "propagation". I'm Using Pega 7.3/7.4.
Context : When I launch my Interaction Portal, I can click on a button "Search" to search a customer. It works 99% of the time, but I want to know what is happening in the 1% (it is generating several problems in the app).
Usually, a new thread appears on the Thread Header my IP and on my ClipBoard (a case is created or opened). Although, in the bad scenario, the thread does not appear in the IP but is present in Clipboard.
I found that the header is from a DataPage called D_CPMPortalRecents.pxResults().
In the ClipBoard, in the bad scenario the .pxResults() are empty (impacting the rest of the application), while in the good scenari, each pxResults() contains the pyId of each thread (i.e. each case).
The DataPage is using has source a Datatransform "RestoreHAPage" with value "D_CPMPortalRecents" as parameter.
I think it's a problem of Data spreading.
All of these are natives functions.
My questions are :
- Did this scenario or a similar case already happen to someone ?
- What could lead to a such problem ?
- What's the utility of the DT "RestoreHAPage" ? (no history nor description)
***Edited by Moderator Marissa to update platform capability tags****
RestoreHAPage is part of the high availability functionality. This should be called when you are trying to restore a session after something like a browser crash. It sounds like the load of that page may be going through that functionality to ensure it works in the HA usecase, though I don't know for certain.
Do you know if the users experiencing this 1% issue are doing things like closing out of their browser without logging out of the Pega application before reconnecting/doing the search? Is D_CPMPortalRecents.pxResults() already null when they go to do a search when they see this issue and the search is just the bit that trips over the underlying problem? Definitely more context around what happens leading up to the problem could be helpful in narrowing things down.
Indeed, the users are used to close the browser directly instead of logging out correctly. We know that this impacts the application but we can't do much thing for this except telling them again to logout first of the Pega app.
We don't know if D_CPMPortalRecents.pxresults() is already null tho, but we will investigate to get this information.
I understand the lack of context is a problem, we will do our best to get and provide enough information.