Posted: 18 Feb 2020 4:57 EST Last activity: 3 Mar 2020 6:00 EST
Consequences of disabling Operator Presence feature.
We dont use Pega Call (CTI) functionality and planning to disable (via DSS : prconfig/operatorpresence/enabled/default to FALSE) Operator Presence feature as it keeps generating unwanted Illegal State exceptions like below :
Please provide instructions to disable Operator Presence feature.I have tried setting the following DSS "prconfig/operatorpresence/enabled/default" to false but it is still not helping (could find log exceptions related to Operator Presence feature).
Provided article refers to Pega Platform 7.2.2 - 7.3 versions,Can you confirm if it is applicable for PRPC 7.3.1 as well ?
Also "Number of concurrent sessions allowed for each operator" feature under your system name rely's on presence records ---- Please provide additional details (additional documentation/articles would be great as well).Also,how do we control concurrent sessions for each operator ?
I have tried disabling Operator Presence feature by settingthe following DSS: prconfig/operatorpresence/enabled/default to FALSE,but still running into the below mentioned different set of related log exceptions.How to get rid of this ?
(Presence_OperatorRecord.Action) INFO 188.8.131.52|184.108.40.206 xxx-
Publish Presence Record starts...
WARN 220.127.116.11|18.104.22.168 xxx - pyModifyUserPresenceAttributes: Exception occured
com.pega.pegarules.pub.presence.PresenceException: Presence Service is Disabled. To enable it use prconfig setting operatorpresence/enabled=true. It needs a server restart
Please find the attachment regarding the complete error stack.