Re-use the Basic Decision Details before Writing Your Own

The Engine includes support for basic eligibility/entitlement decision details (see Basic Eligibility/entitlement Decision Details).

Consider re-using this basic display category before implementing your own (more suitable) display categories. This re-use will help you understand how decision details are implemented and will enable your testers to see more details about your cases (albeit only very basic details).

You can remove the Basic display category later when you implement more appropriate display categories.

To re-use the basic decision details, follow these steps (as part of the general steps involved in implementation decision details - see Implementation):

• When you create your case rule class (see Write the Case rule class), make your rule class extend AbstractBasicProductDecisionDetailsRuleSet.AbstractBasicCase. You must implement the inherited abstract abstractCase rule attribute, to create an instance of the underlying rule class for your eligibility/entitlement (i.e. the one you created in Write the Case Eligibility/Entitlement Calculation Rule Classes), specifying the value for productDeliveryCase; and
• When you create you create your dynamic UIM and properties files, clone those for the following pages to your custom component:
  • CREOLEDisplayRules_basicCaseDisplay; and
  • CREOLEDisplayRules_basicCaseDisplay_objectiveTagSubscreen.

  You must provide new unique names for your cloned dynamic UIM and .properties files, and update their contents to point to your new names.