Refresh on Pega Mashup portal is logging the agent out after disabling the operator and reinstall it
Use case:
Operator profile is changed in CRM and propagated to PEGA via REST API which gives the correct new profile. PEGA is then expected to terminate and re-create the operator whatever is "online" or not, refreshing the portal is making the system to re-read the new profile so operator is available again with new attributes and privileges. this is transparent to operator himself who will not be logged out but will be restablished to the same screen after manual refresh.
Operator is working on a front end portal which is connected to PEGA via Mashup, when API comes to change his profile it all works fine when the agent/operator has opened a case, it is not working when agent is on a dashboard, always from front-end via PEGA Mashup, let's say a data-portal harness.
In this last case when change profile API is received the operator when manually refreshing from a PEGA button action, is logged out and need to re-login to enter its portal again, this is NOT WANTED from our customer.
The same is not happening when refreshing the browser which will make the whole operation working fine, operator is not logged out in this case and can proceed working with new attributes
Please note that:
Refresh action has been tested and changed for multiple options like Refresh this Section / Harness etc etc all giving the same result
Use case:
Operator profile is changed in CRM and propagated to PEGA via REST API which gives the correct new profile. PEGA is then expected to terminate and re-create the operator whatever is "online" or not, refreshing the portal is making the system to re-read the new profile so operator is available again with new attributes and privileges. this is transparent to operator himself who will not be logged out but will be restablished to the same screen after manual refresh.
Operator is working on a front end portal which is connected to PEGA via Mashup, when API comes to change his profile it all works fine when the agent/operator has opened a case, it is not working when agent is on a dashboard, always from front-end via PEGA Mashup, let's say a data-portal harness.
In this last case when change profile API is received the operator when manually refreshing from a PEGA button action, is logged out and need to re-login to enter its portal again, this is NOT WANTED from our customer.
The same is not happening when refreshing the browser which will make the whole operation working fine, operator is not logged out in this case and can proceed working with new attributes
Please note that:
Refresh action has been tested and changed for multiple options like Refresh this Section / Harness etc etc all giving the same result
When refresh is performed I can see from the network tracer an error saying that "websocket is not connected", while on a successful case with work object that is working fine (see snapshot attached)
Mashup configuration is the same for work object and portal, Pega version is quite old (8.7).
HCA Healthcare
US
@manse The issue occurs because updating the operator profile via API may disrupt the WebSocket connection used by Pega Mashup to maintain the session, leading to logout when refreshing on a dashboard. To resolve this, ensure Mashup uses token-based authentication to prevent session invalidation. Adjust operator session policies in Pega to ensure the profile update does not terminate active sessions. Instead of a full section or harness refresh, try reloading specific components using dynamic data pages to fetch updated attributes without reinitializing the session. As a workaround, implement JavaScript in the Mashup container to detect the profile update and trigger a browser-level refresh (e.g., location.reload()) to prevent logout. Upgrading Pega to a newer version (e.g., 8.8 or later) may also address the issue, as it includes improved WebSocket handling and Mashup integration. This ensures operators stay logged in while their profile updates are applied seamlessly.