The Application Preflight tool reports the results of several checks on the rules in the currently selected application. These checks encourage good design and implementation practice, as codified in the guardrails and elsewhere.
A rule in your application may work correctly and save
without errors, but still be marked with a warning (). The Application Preflight tool summarizes these
warnings.
For example, a decision table rule may contain two rows that conflict — give a different result for the same inputs. You can save the decision table rule and execute it within your application, because the uppermost row of the table is used at runtime, and other conflicting rows are ignored. However, the conflict may indicate that the rule was not entered correctly.
You can perform the preflight check at any time during
development. As a best practice, use the Application Preflight
tool before you lock a RuleSet version. Research each warning
message.
Warnings are instances of the Index-Warning
class, which corresponds to the pr_index_warnings
database table.
Warnings appear only when a rule
is saved in a V4.2SP6 or
later system. Rules saved in earlier versions and not yet resaved in a
newer system do not include warnings.
![]() |
conflict, guardrail, warning icon |
![]() |
About the Application Preflight tool |