When you save a rule form and a warning icon () appears, one or more warning conditions were detected. Warning conditions do not prevent the rule from saving.

Warning conditions identify unexpected and possibly unintended situations, or practices not recommended, or variances from best practices. Consult the messages at the bottom of the form for additional details on each warning.

To review all the warnings for the rules in an application, use Application Preflight tool.

For many rule types, you can extend the set of warnings with a custom activity named Rule-ZZZZ.CheckForCustomWarnings, where Rule-ZZZZ is a rule type. Pega Developer Network article PRKB-21872 How to create a rule warning and Standard activities — Extension points

Warnings are maintained as instances of the Index-Warning class and saved in the pr_index_warnings database table. (This class and table were introduced in V4.2SP6. Rules saved in older systems and never resaved in a later version provide a different approach to warnings.)

The standard decision tree rule Embed-Warning.pxWarningDetails controls whether warnings of a specific type are reported in the Application Preflight tool. By default, all are reported; you can override this decision tree rule to choose which to omit. This decision tree tests the property pxWarningType, which can have values indicating the source of the warning, such as:

• Java — an activity contains a Java step
• API 02 — an activity uses the Version 3 PublicAPI
• WriteNow — An activity step includes a method with an immediate database write operation rather than a Commit method.

	guardrails, preflight check
	About the Application Preflight tool

Definitions — W