Question
Philips Home Monitoring
US
Last activity: 19 Nov 2015 10:43 EST
In Pega 7.1.7 have One Operator in One Pega Environment that does not remember open screens / history any thoughts on why?
In one of my pega environments (Development) for one user (me) it is not remembering recent history or open tabs between sessions. Also pega6 under Operator preference there was a way to tell it remember screens but under Pega 7 that option is no longer there.
Steps to Reproduce
1.) Open Pega 7 in Dev under myself
2.) Do some actions and see recent history getting recorded
3.) open a few rules (checked out and not checked out)
4.) Log off Pega
5.) Log back in
6.) None of the open tabs are remembered and history is empty.
Attempted Solutions
under Operator preferences I reset to default preferences -->tried again same results.
Tried on difference client machines same results
Operator has same Access Groups and permissions as other users.
Reviewed the article: https://pdn.pega.com/designer-studio/about-the-pega-7-designer-studio and did not find any information on how the operator preferences have changed from 6.0 to 7.0
Accepted Solution
Philips Home Monitoring
US
working with Kip we finally resolved the issue!
We were looking into PR_DATA_RECENTS to see if the data was being written and it was not. Through various logging debug errors include on the recents rules, we noticed that there was an exception being throw about unable to write to table with no description as to what the problem was.
Further investigation in PR_DATA_RECENTS table gave us our answer.
Instead of looking PR_DATA_RECENTS for RECENT activity, we looked for PXUPDATEOPNAME=<operator id lowercase> and found no rows still. When we did lower(PXUPDATEOPNAME)=<operator id lowercase> and found old records in PR_DATA_RECENTS from may that had the operator id in mixed cases. Not sure why it was like though. We then updated these rows to be lowercase operator_id instead and then the recent history started working again for that operator.
Pegasystems Inc.
US
Hi Bob,
Just a few points of clarification on this issue:
The following PDN post exhibits the privileges required for using the Recents Explorer --> https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
This PDN Post provides information on Designer Studio Preferences --> https://community.pega.com/sites/default/files/help_v717/basics/v6portal/v6preferences.htm
- Do you log in via single sign on? If so, what is the behavior if you log directly into Pega? Do you have custom authentication which may not be allowing the save of the recent history?
- If this problem is only occurring for your user, have you compared a working and non-working user?
Please provide screen images of this comparison so community members can assist.
- Also, provide a screen image of clipboard information including the User Page Declare_pzRecentsCache and the Thread-level Data Page Declare_pxRecents.
Philips Home Monitoring
US
Kip,
Thank you for your response. I will check out the links you posted. In the meantime, to answer your question, in this particular environment I am NOT using SSO and using the prweb/PRServlet url instead of the /prweb/PRWebLDAP1 url.
I'll check privileges but to be clear I am seeing Recent History WHILE I AM WORKING. If I log off and come back the Recent History is gone.
Bob
Pegasystems Inc.
US
Hi Bob,
Please gather Tracer output from a login for a working and non-working user. You can initiate the Tracer via SMA. You can send me the Tracer output by attaching it the Discussion or sending it directly to me.
Accepted Solution
Philips Home Monitoring
US
working with Kip we finally resolved the issue!
We were looking into PR_DATA_RECENTS to see if the data was being written and it was not. Through various logging debug errors include on the recents rules, we noticed that there was an exception being throw about unable to write to table with no description as to what the problem was.
Further investigation in PR_DATA_RECENTS table gave us our answer.
Instead of looking PR_DATA_RECENTS for RECENT activity, we looked for PXUPDATEOPNAME=<operator id lowercase> and found no rows still. When we did lower(PXUPDATEOPNAME)=<operator id lowercase> and found old records in PR_DATA_RECENTS from may that had the operator id in mixed cases. Not sure why it was like though. We then updated these rows to be lowercase operator_id instead and then the recent history started working again for that operator.