Skip to main content
Contact a Moderator

Question

3
Replies
1576
Views
 Anthony Gourtay (Anthony_Gourtay)
Capgemini Engineering
Business Application Expert
Capgemini Engineering
BE
Anthony_Gourtay Member since 2017 16 posts
Capgemini Engineering
Posted: December 19, 2018
Last activity: December 18, 2019
Posted: 19 Dec 2018 2:17 EST
Last activity: 18 Dec 2019 15:08 EST
Closed

Operator Presence and prconfig.xml

Hello,

in our prconfig.xml we've added below line

<env name="operatorpresence/enabled/default" value="false"/>

As per some articles this should disable operator presence follow-up

Yet, in our logs, we still receive:

Caused by: com.pega.pegarules.priv.presence.PresenceRuntimeException: presence record resulted a no matching records operator operatorID, tenantHash: shared, requestorId: HP85MMUPDQLM69MP282T37HGPB9FDRDM9 - usually this should not happen

This application is running with PEGA 7.3.1 / WebSphere 8.5 / Oracle 11G

Is there anything else to consider to remove operator presence check or the config line if not correct or not the correct one?

Thank you

Regards

Anthony

Pega Platform
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 10 Jan 2019 2:55 EST
Waseem Khan (khanw2)
PEGA
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Anthony,


Please create a DSS " prconfig/operatorpresence/enabled/default " in the Pega-Engine (Owning Ruleset) and set the value to false and try.


I did find similar article related to this issue and I could see the same solution is suggested. Please refer below article.


https://community.pega.com/support/support-articles/performance-degrades-when-users-log-same-operator-id


 


 


 
Posted: 3 years ago
Posted: 10 Jan 2019 3:05 EST
Anthony Gourtay (Anthony_Gourtay)
Capgemini Engineering
Business Application Expert
Capgemini Engineering
BE

Hello,


I'll try. Any idea about the reason/circumstance a parameter in prconfig.xml would not work and would work as a DSS?


Thank you


Regards


Anthony
Posted: 2 years ago
Posted: 18 Dec 2019 15:08 EST
Brett Allen (BrettAllen)
PEGA
Principal Technical Architect
Pegasystems Inc.
US

I think you would need to leave off /default in your prconfig.xml.  This should work:


<env name="operatorpresence/enabled" value="false"/>

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice