Your rule class to identify and calculate decision details for a particular display category on a case must ultimately extend from the ProductDecisionDetailsRuleSet.AbstractCase interface rule class. For ease of upgrades, it is recommended that your rule class extends the DefaultProductDecisionDetailsRuleSet.DefaultCase rule class which provides default implementations.
Here is a description of the attributes inherited from AbstractCase:
| Rule Attribute name | Data type | Description |
|---|---|---|
| productDeliveryCase | ProductDeliveryCase | The controlling rule object which is responsible for splicing together the determination result from the contributions made by the product period. Passed in when the instance of AbstractCase is created. |
Create a rule class which extends DefaultProductKeyDataRuleSet.DefaultCase. The rule class should be named in line with your product and display category, e.g. ProductNameDisplayCategoryName (the Engine does not have any technical constraint on the rule class name - rather a good name for your rule class may make it easier to develop and maintain your rule sets).
The inherited implementation from DefaultCase means that you have a valid rule class for use with decision details, but as yet your rule class will not gather any useful data for display.