Reply posted on November 27, 2019 by PradeepChowdaryP
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 Anthony Tham for achieving the title of Participant of the Week! Anthony proactively assisted several users with their queries, which helped them progress with the troubleshooting and arrive at successful solutions. We appreciate your efforts to share knowledge in the community. Hope to see you around and keep up the great work!
Just to confirm, you had a list view with an OOTB getContent activity, where even though the filter conditions included pxCoverInsKey, it was not included in the WHERE clause? If this is the case, it sounds like a bug. The query generation code has...
Thanks Kevin, the duplicate entry is being set by start script, once I fixed it logging is working.
These models are not supported in 8.3. The complete list of supported models (until PMML v4.3) is here- https://community.pega.com/knowledgebase/articles/decision-management-overview/supported-pmml-model-types
Adding to above when you set-Dnodetype=stream, the nodes automatically start to add the stream landing page. For starter try keeping only one node as stream make it stable and then add the other node based on port configurations as suggested above
Hi, This is a bug. I guess you need HFix-42336 (This one for for 7.3.1, looks like you are also using 7.3.1). Raise a SR and check this one. Also check https://community.pega.com/knowledgebase/articles/pega-sales-automation-hotfixes there are few...
You need to observe the PegaRULES and PegaRULES-ALERT logs which are generated on the VBD node at the point of the issue and see if you can get any clue. You can also take the thread dump and you can analyze the thread dump using several tools which...
I had same issue when using windows 7, Tried today on Windows 10, I was able to add node and initialize the application.
I see this issue in Pega OOB 8.3 and have not seen any issues as well. This looks like its a data-engine bug. If you go to the External Mapping table and try to open any of the mapped properties, they all correlate. Those are the key fields.
Please wait while we search for PDN content that suits your question.