About configuring a new validation or override rule

You can create new validation or override rules.

A new validation rule is based on:
  • Validation type
  • Template. The input template is the XML template that is used to create input data to pass to the condition evaluator.
  • Greex rule
  • Data capture value
  • The lane type, store type, and region to which the validation rule applies

Override rules are created similarly to the validation rules, with the exception that approvers can be assigned for each override rule and multiple override rules can be assigned to a validation.

Example: maximum number of coupons

An enterprise E1 generally restricts the number of coupons that are allowed to five per order for most of its customers. An exception is a "Gold" customer, who is allowed to use 10 coupons. For both types of customer, managers are allowed to grant some exceptions. Here are the rules that apply to the transactions:
Table 1.
Validation rule Override rule User scenario
For enterprise E1: Maximum number of coupons that are allowed per order = 5 Rule 1: If (CustomerType=’GOLD’ and NumberOfCoupons<=10), then approval is not required. This rule is an allow rule. A "Gold" customer presents 9 coupons at checkout. No approval is required.
Rule 2: If (CustomerType=’OTHER’ and NumberOfCoupons>10, then transaction is not allowed. This rule is a disallow rule. A customer without Gold status presents 15 coupons. The manager does not have authority to allow the use of the last 5 coupons.
Rule 3: If (CustomerType=’GOLD’ and NumberOfCoupons > 10, then manager approval is required. This rule is an approval rule. A Gold customer presents 15 coupons. The manager allows the transactions.
Rule 4: If (CustomerType=’OTHER’ and NumberOfCoupons>5), then approval is required. This rule is also an approval rule. A customer without Gold status presents 10 coupons. The manager allows the transactions.