Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Incorrect Pega Guardrails - Compliance Score report



The Pega guardrail report is giving an incorrect picture of the actual guardrail compliance of project. A significant bulk of the warnings are related to ABV rulesets (about 90% for each contributor) and this gets repeated for all contributors.

Error Messages

Warning Severity
Warning Type
Warning Name

Steps to Reproduce

Generate Pega guardrail report.

Root Cause

This issue was determined to be a product enhancement request.
Unlocked ABV rulesets should belong to one Rule-Application (but can belong to more than one version). This prevents ABV rulesets from referring to rules that may not exist in all applications that the ruleset is contained in.

For parallel development, use ABV-branched rulesets that can access all rulesets in the application, including other rulesets in the same branch, as well as any other branches included in the same application definition.

The risks add up as more users use ABV rulesets that may be referring to rules that may not exist in all applications that the ruleset is contained in, and that's why the guardrail score goes down by the user count.


An enhancement request, FDBK-20104, has been created for consideration by Pega Product Management.

Published August 26, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us