Validating a component


<[^>]+?>","")" class="contextID">

To quickly determine whether a component's signature conditions are valid on its associated target server, you can run a short validation process on any existing component.

This validation process is useful in the case of components that you created manually, or if you need to re-validate a component after modifying the signature in the component template.

To validate a component based on its signature

  1. Through the Component Templates, Components, or Servers folder, navigate to the component that you want to validate, right-click it, and select Validate.
    The Validate window is displayed. This window is divided into two panes. The top pane displays the full signature as defined through the Rule Editor, including all of its conditions and if-then conditional constructs.
  2. Click Run Test at the top right corner of the Validate window.
    The signature rule is validated. Any condition within the rule that caused the rule to end in Non-compliant status appears in red in the top pane. The bottom pane displays compliance details for a selected condition.
  3. In the top pane, select a condition within the signature.
    In the bottom pane, the condition is parsed into columns for the left-hand-side (LHS) operand, comparison operator, and right-hand-side (RHS) operand. An additional Result column indicates whether the component satisfied the condition (either for true or for false). The actual value detected on the target component appears in brackets after the LHS operand so that you can see how it compares to the value in the RHS operand.


    In the top pane, condition operands that are very long are truncated and end with an ellipsis (...).
    Cardinality conditions are not parsed in the bottom pane. A basic condition is not parsed if it contains wild cards and was satisfied by the component.
    If a basic condition is preceded by a NOT logical operator, the Success column in the bottom pane shows a value of true when the condition appears in red in the top pane.
    Lines that were not analyzed appear in gray in the rule in the top pane. For example: if, then, or else blocks in a conditional construct that were skipped or not reached.
    In a conditional construct only one then line, or the last else line, may appear in red. All if and elseif lines always appear in black font.

Was this page helpful? Yes No Submitting... Thank you