Links may not function; however, this content may be relevant to outdated versions of the product.
Guardrails compliance score
You can assess the overall quality of an application by referring to its compliance score. A compliance score provides an executive-level summary of whether your application is guardrail-compliant. You can improve your compliance score, and avoid potential maintenance and performance issues by reducing the number of warnings in your application. In Designer Studio, you view the compliance score for an application by clicking Designer Studio > Application > Guardrails > Compliance Score.
Compliance scores range from 0 to 100, with 100 representing the highest possible score:
- A score of 90 or greater indicates your application is in good standing. As a best practice, verify that an application has a score of 97 or greater before deploying it to your production system.
- A score of 80 to 89 indicates your application needs review for improvement.
- A score below 80 requires immediate action.
Compliance Score tab of the Application Guardrails landing page
In Designer Studio, the Compliance Score tab of the Application Guardrails landing page displays the following metrics:
- Compliance score – A weighted score for each application that measures overall compliance with application design best practices, or guardrails.
- % Compliant rules – The percentage of rules in your application that do not have severe, moderate, and informational warnings.
- Total rules – The total number of rules in your application.
- Rules with warnings and Rules with unjustified warnings – The number of rules with warnings and unjustified warnings. Click the number to view a list of rules by name, ruleset, rule type, applies to class, the last update time, and who made the last change.
The Warning Details tab provides a centralized view of these warnings, with more information on the actions you can take to resolve them.
To generate a compliance score, the Pega Platform calculates a weighted numerator based on the number of severe and moderate warnings in the application. Then, the system makes a comparison against the remaining number of rules in the application that have caution-level or no warnings. The result is converted to a percentage, protecting against any negative values, as outlined in the following formula:
The variables in this formula are interpreted as follows:
Sev1u – The number of unjustified, severe (severity level 1) warnings in the application.
Sev2u – The number of unjustified, moderate (severity level 2) warnings in the application.
Sev1j – The number of justified, severe (severity level 1) warnings in the application.
Sev2j – The number of justified, moderate (severity level 2) warnings in the application.
Total Remaining Rules – The sum of rules with caution (severity level 3) warnings and rules with no warnings in the application. This value excludes property rules and rules that reside in a Pega-* ruleset.
Previous topic Developer best practices using Pega Platform Next topic Compliance score trend reporting