Question
Capgemini Engineering
BE
Last activity: 18 Dec 2019 15:08 EST
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
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.
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
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"/>