Question

8
Replies
711
Views
John Bushey (JohnB381)
Pega

Pega
US
JohnB381 Member since 2016 9 posts
Pega
Posted: June 15, 2016
Last activity: July 28, 2016
Posted: 15 Jun 2016 14:34 EDT
Last activity: 28 Jul 2016 11:34 EDT
Closed

pzWarningsIntroduced and similar reports

Reports like pzWarningsIntroduced trigger lots of Pega0005 alerts because the query logic is so complicated.   The complexity is caused by using the rule resolution and/or application filter check boxes in the report definition rules.   Pega ships many reports like this that trigger alerts and at times prevents functionality from working.   A common work around is to use a private checkout on PRPC reports and disable the filters.   I've also seen several PDN articles telling users to update the Guardrails section used by  each rule to stop using the pzWarningsIntroduced -thus masking warnings.  

My team has not been able to tune the rules tables to improve the performance of these queries.  At times we have to resort to unnatural things to work around these problems and unblock development.

Is there any solution to this problem?

Thanks

John

Message was edited by: Lochan to add Category

Reporting
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.