Conditions can be used in a QA Build program to determine which actions to
perform. For example, you can set a condition to enter a procedure. If the
condition is not met, the procedure is not executed and the program continues
with the next procedure. Conditions are expressed using Boolean expressions such as customer.balance < customer.credit_limit
Each condition can be associated with an error message that is displayed if the condition fails. It sometimes happens that you may want to display an error message for a condition without otherwise altering the path of the program. This is achieved through Warning Only conditions. Also a condition can be divided into multiple parts, either because it is very complex, or because you want to display different error messages depending on which part of the condition failed. For multi-part conditions you can decide whether or not to carry on testing the condition when one part fails.
Conditions can be used before or after performing many actions, for example:
deciding whether or not to:
total one field in another
checking validity:
of a record accessed
filtering the records to be processed in a batch process or offered to the user in a multiple choice pop-up window
Formulas can be used in field processing to assign values to fields. For
example to determine the order line value by multiplying
the price by the quantity you could use the following simple formula:
item_price * quantity
The expressions for conditions and formulas use the same syntax and support the same range of operators and functions. The only difference is that the expression for a condition must always evaluate to TRUE or FALSE. That is, it must result in a Boolean (Yes/No) data type. The expression for a formula must result in the data type of the field to which it is assigned.
Both Formulas and Conditions are created using the Formula Editing Menu.