Creating a Receipt Handling Rule

Objective

After completing this lesson, you will be able to configure a receipt handling rule.

Receipt Handling Rule Considerations

When creating or editing conditional expressions for receipt handling rules, you should consider the following:

  • It's recommended to make copies of the receipt limits that are pre-built and then modify the copies.
  • An expression can include an unlimited number of conditions.
  • It is composed of two conditions, separated by the boolean separator of And.
  • Most conditions are composed of a Field followed by an Operator and a Value.
    • An Operator is one of several pre-defined comparison operators (equals, not equals, is greater than, and so forth). The list of operators changes depending on the type of data being compared.
    • A Value is a constant, and like the field, can be of any data type; however, the data type of the value must match the data type of the field.
The image displays a two‑column table labeled Field and Description. It explains options for building rule conditions. Rows include Left Parenthesis, Data Object, Field/Value, Operator, a Data Object row that is fixed to Value, Field/Value again, Right Parenthesis, and And/Or. The descriptions note that selections come from a helper pane based on the chosen Data Object, parentheses are optional, the fixed field shows Value and cannot change, and And/Or links the current condition to the next. No areas are highlighted.

Summary

  • Create receipt handling rules by copying and modifying existing ones.
  • Rules can have unlimited conditions, typically using "And" to combine them.
  • Conditions use fields, operators, and values; data types must match.
  • Operators are pre-defined comparisons (equals, not equals, etc.).
  • Values are constants; their data type must match the field's.