What Motivates You to Participate Here in the PSC?
Reply posted on October 7, 2019 by singamanenip
Hi Parvin, Can you please share the details on how you resolved the issue, if resolved?
Reply posted on October 7, 2019 by VeeraSaddala
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 "...
Reply posted on October 7, 2019 by KevinZheng_GCSPega
This probably needs time to try and investigate. From your side, have you already tried but with some difficulties? Please elaborate.
Reply posted on October 7, 2019 by SantoshP2386
After upgrade to 8.2.3 we are also seeing similar log messages. More surprisingly we are not using kafka.
Reply posted on October 4, 2019 by LONGJPega
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,...
Reply posted on October 4, 2019 by Ravi Kumar Pisupati
Thank you Rett for the quick response and will check on it. You are always helpful, I know. Thanks, Ravi Kumar.
Reply posted on October 4, 2019 by KevinZheng_GCSPega
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.