Assessing Guardrail Compliance

Pega monitors your application for configurations that lead to maintenance or performance issues. By addressing these issues, you improve application quality and prevent performance issues for users.

Guardrails

1. To help you develop high-quality applications, Pega monitors your application for compliance with application design best practices (guardrails).
2. When a rule in your application violates one or more guardrails, Pega notifies you with a rule warning that prompts you to review the deviation and update your application prior to release.

Compliance Score

1. The compliance score measure overall compliance with Pega 7 Platform best practices.

   Measures the number of rules with severe/moderate warnings, compared to the number of rules with caution level warnings or no warnings.

   Indicates the impact of complex or custom code on application maintenance and performance.

2. Use the compliance score to measure the quantity and severity of rule warnings in your application.

How to Access the Guardrail Compliance Score

1. Use the Guardrails landing page to assess application quality.
    Select Application > Guardrails from the  Designer Studio menu. 
2. Review the compliance score and any rule warnings.

Compliance Score Rankings

Pega assesses the rules in your application and calculates the compliance score on a scale of 0-100, where 100 is the best possible score.

1. A score of 90 or greater indicates your application is in good standing.
2. A score of 80-89 indicates your application needs review for improvement.
3. A score below 80 indicates that your application requires immediate action.

Warning Summary Tab

1. The Guardrails landing page also categorizes the rules in your application that include warnings.  
2. The Warning Summary tab presents two bar charts that report the number and severity of rule warnings in your application, organized by rule type.Use the information on this tab to determine which parts of your application generate the greatest number of rules with warnings.

How to Analyze Risk Areas

1. Use the Compliance Details tab to view three options for analyzing risk:

   Warning impact: The severe and moderate configuration issues to address before release.  
   Warning age: The age of the warnings in your application. 
   Application risk introduced by operator: The developer(s) responsible for introducing the behavior generating the warnings.

2. Resolve the issues in the Warning impact section first.   
3. The list is organized by warning type, and highlights the warnings with the greatest impact on the compliance score.
4. Click each number to view the list of rules that violate guardrails.  
5. The rule that contains the warning opens when a rule warning is selected.
6. Pega displays the rule warning at the top of the rule form.