When we run the application, whenever a new intent is launched from interaction, or an intent makes progress in the flow, such as submit a flow action, then the layout aforementioned in the header refreshes itself, even though neither D_CPMPortalContext.pyID or D_CPMPortalContext.InteractionHeaderRefreshDateTime changes, both remain the same.
Investigation shows that PRPC server somehow thinks that D_CPMPortalContext.pyID has changed, and tells the browser the same, causing browser to refresh the layout aforementioned.
Has anyone noticed same issue in your CPM application?
***Edited by Moderator Marissa to add SR Details***
>>> Investigation shows that PRPC server somehow thinks that D_CPMPortalContext.pyID has changed
You may want to use the Pega tracer and search through the gathered trace for references to D_CPMPortalContext.pyID. But be careful not to merely use string search, as the data page may itself take parameters, which means the actual data page name could be "decorated".
But seeing all the values shown in the tracer for the .pyID property on ANY data page whose name CONTAINS "D_CPMPortalContext" may help explain what's happening.
I am not asking how to troubleshoot. I am asking whether this is a known, or unknown, defect in CPM. We are using pretty much the OOTB rule in CPM framework. What I have observed and described should not occur.
I have seen many similar posts, and I have confirmed on my system that the same refresh happens. I'm not sure why it does, but, yes, the same thing happens to everyone.
If you feel that this is unacceptable, you could raise an SR to get this looked at. Either you'll get an explanation of why this must be the behavior, or else possibly a local change to avoid it, or a promise of a fix.