The rule package that is created for this example is called my.test. Three rules are defined within the package. Two of the rules are defined as two rows of a single Decision Table, which is created at the Finance Department node of the business structure.
The rule checks two conditions:
- The value of the segment property of the Customer fact
- The value of the order property of the Customer fact
If the conditions are all true, the rule will fire a single action, which is to set the value of the offer property of the Customer fact to 1.
The third rule is defined as a linear rule and has been created at the Accounts Payable node of the business structure.
This rule checks the same conditions—and has the same action—as the rules that are defined at the Finance Department node. Normally, you might expect this rule to be a third row in the earlier decision table, at the Finance Department node. It is included here only to demonstrate how the rules at different nodes in the business structure can be evaluated.
The my.test rule package is deployed to the Genesys Rules Engine or (since release 8.1.2) an application cluster. When two or more conditions are listed, there is an implied “and” between them. So, this rule is saying that “when the customer segment is bronze and the order value is greater than 8000, then offer special promotion”. The rule author can also choose other logical operators, such as or, not, and not, and so on.