11.1 Boolean Deciders

Whenever the XML allows a boolean decider (instead of a concrete boolean), these are the valid options:

11.1.1 Comparison Operation

A comparison can compare dates or strings. Whenever a boolean decider is expected in the XML, the comparison attribute can be added, with a value of:

A comparison requires an attribute type which must be "string" or "date". If unknown or missing, Viewpoint assumes "string".

All comparison operations require <first> and <second> elements (which themselves could be deciders). The type of decider is dependent on the type attribute. If the type is "string" the first and second values should be string deciders. If the type is "date", the first and second values should be date deciders.

In the example below, the requirement evaluates to true if the value in the "procs" component is equal to "1".

<requirement comparison="equals">
 <first>
  <component id="procs" />
 </first>
 <second>1</second>
</requirement>

11.1.2 Logical Operation

A logical operation decider takes any number of children boolean operation deciders and performs a logical operation to determine the final boolean value. The two types of logical operations are:

To specify the type of logical operation, use the logical-operation attribute with one of the above values. All logical operations require at least two children.

In the example below, the requirement is evaluated to true if either the "test_vlan" or "dev_vlan" components are true.

<requirement logical-operation="or">
 <value>
  <component id="test_vlan" />
 </value>
 <value>
  <component id="dev_vlan" />
 </value>
</requirement>