Reply posted on July 8, 2019 by RadoslawNowakPega
I fully agree, Rob. I will ask an Engineering team to investigate and fix the issue.
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Gouri Shankar for achieving the title of Participant of the Week! Gouri Shankar believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. Keep up the great work!
Update: It has come to my attention that this is a known issue with the PEGA native app. When I can post a support request in MSP (My Support Portal), I will open a ticket. To receive a response/fix from the PEGA team.
This should not be related to AES, AES is just a monitoring tool and not administrative one. One printed in log suggests there are genuine thread dumps which should be reviewed.
As per our discussion in the SR, the reported behavior is working fine after performing the below steps. 1) Run the Activity "MonitorIndicators" manually 2) Open the Clipboard, go to thread "Quiesce Management" thread, go to Data...
Hi David, Yes, these options are independent from each other. You can use OpenCTI without using Avaya AES. There is no mention of Avaya in the OpenCTI installation guide.
Hi Karthik, Why don't you use PDC that is available for onpremise customers also.Please find more information about pdc below. https://community.pega.com/knowledgebase/products/predictive-diagnostic-cloud Thanks, Abhinav
Add <env name="initialization/urlencryption" value="false" /> in prconfig.xml, it will resolve the problem. Regards Bhagath Vasireddy
Please wait while we search for PDN content that suits your question.