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.

Justifying an application warning

Suggest edit Updated on April 5, 2022

Justify a warning to explain why your application is exempt from a best practice, or guardrail. By documenting which warnings are intentionally unresolved, you can improve your compliance score.

Before you begin:

Ensure that your access role is associated with the pxAllWarningJustification privilege.

  1. In the header of Dev Studio, click ConfigureApplicationQualityGuardrailsCompliance Score.
  2. In the Compliance score section, click the number in the Rules with unjustified warnings field.
  3. In the Rule name column, click a rule to open it.
  4. In the header of the rule form, click Review/Edit, and then review the warning to confirm that your application can tolerate the associated risk.
  5. Click Add Justification.
    Note: You cannot justify some warnings, because the risk that they introduce is too severe. For these cases, consider resolving the warning instead.
  6. In the field that is displayed, enter text that explains why your development team chooses to leave this warning unresolved.
  7. Click OK.
  8. Click Save.
What to do next: Periodically review the list of rules with unjustified warnings in your application because imported rules can display new warnings when your development team resaves them.
    Did you find this content helpful? YesNo

    Have a question? Get answers now.

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

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

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us