CPM Portal Recents tabs- sluggish, Not Robust enough
We recently upgraded from v5.5 to 7.1.9 (CS 7.1.4). After relesed to prod.. we are receiving complaints from users that work object tabs navigation ( CPMPortal Recents gadget which shows open workobjects in tabs ) is sluggish, sometimes dont espond properly and so on ... not providing good user experience
1> When multiple works objects are kept opened and in mid of taking the call or working on new Interaction, when you try to navigate to other tabs, that tab dont gets focus but screen navigates to that work. Some time viseversa, tab gets the focus when clicked but work object screen still stays in previous tab.
2> When work processing end up in some error or exception, that screen sit on top of Home tab and you can never get rid of it... you refressh browser or relogin .. still Home tab is replaced with thaty error/grey screen. Only if you use browser (File- New Session) and relogin ... then only it shows back Home portal.
Based on user comments and our analysis, the Page group this CPM Portal Recents gadget workon .. if somehow it gets corrupted with some invalid data, user starts expienecing above issues.
Can Pega team looks at this issue.. Tabs should be robust and navigation should be seemless... If one tab has issues.. it should not break all othetr tabs which has correct screen...
***Updated by moderator: Vidyaranjan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option.***
There are few concerns raised by other Users as well regarding Tabs funcationality but most of them are addressed on case by case basis.
1. Your first concern regarding multiple work objects beeing kept open.
When you say multiple, is it greater than 10. Because currently we suggest that open work objects number be kept under 10 (which is configurable) this includes Interactions (I- cases) and intent tasks(S- cases) are open.
2. I suggest you raise an SR for this scenario. An hotfix might already be present. We just want more details of the issue usecase.