Reply posted on October 8, 2019 by AnirudhJ
Pega Version 7.2
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!
FYI: If you're trying to set prconfig setting using DSS, you need to prefix "prconfig/" (as you have) as well as suffix "/default". I'm not sure this would work for these settings, so the safe bet is to modify your...
Hi Vikash, Thanks for your message and sorry for the late response. I have checked the pxresolvedtimestamp for the cases resolved with custom status. I don't see the property has a value. We do have few case types resolved with the status "...
This probably needs time to try and investigate. From your side, have you already tried but with some difficulties? Please elaborate.
After upgrade to 8.2.3 we are also seeing similar log messages. More surprisingly we are not using kafka.
Collation is decided upon the customer's own globalization/localization requirements. The major difference between Latin1_General_CI_AS and SQL_Latin1_General_CP1_CI_AS is the character expansions. Depends on how would you require the behavior,...
So this is very likely on the WebSeal configuration side. Check with your WebSeal admin first. I have attached an internal document for your reference, use that as a general guide.
In that case, I suggest you redeploy the SMA. I have experience in the past this could resolve the issue.
Please wait while we search for PDN content that suits your question.