Show Table of Contents
23.2. Pricing Rule Example: Decision Table Configuration
Figure 23.1. Decision Table Configuration
- The
RuleSetdeclaration provides the package name. There are also other optional items you can put here, such asVariablesfor global variables, andImportsfor importing classes. In this case, the namespace of the rules is the same as the fact classes and thus can be omitted. - The name after the
RuleTabledeclaration (Pricing bracket) is used as the prefix for all the generated rules. - "CONDITION or ACTION", indicates the purpose of the column, that is, whether it forms part of the condition or the consequence of the rule that will be generated.
- The driver's data is spread across three cells which means that the template expressions below it are applied. You can observe the driver's age range (which uses
$1and$2with comma-separated values),locationRiskProfile, andpriorClaimsin the respective columns. - You can set a policy base price and message log in the Action column.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.