@Pawel Sobolewski  Warnings in Pega are designed to draw your attention to configurations that may introduce potential risks to your application, including performance, data integrity, and maintainability. Even if these warnings are in auto-generated rules, they serve as checkpoints for you to review the configuration.

If you believe the warning is justified due to your application's specific requirements, you can justify the warning. Justifying a warning explains why your application is exempt from a best practice, or guardrail. By documenting which warnings are intentionally unresolved, you can improve your compliance score. However, it's important to note that a justified warning still has an impact on the compliance score, but it's 5 times less than an unjustified warning. If you're required to maintain a certain compliance score, you should aim to resolve as many warnings as possible and justify those that are necessary for your application's functionality.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references

Resolving an application warning

Compliance score logic

LSA Data Excellence: Eradicate or Justify Guardrail Warnings raised when using

 Justifying an application warning

Improving your compliance score