A System Administrator Creates and Publishes Rule Set Information for a Product

Before any kind of eligibility and entitlement processing can occur for a Product, that Product must first be created and rule set information for that Product published. For details on how a Product is built, see the see the How to Build a Product guide.

In this example, the Product is for a Sickness Benefit. The system administrator sets up the new Product details, associates rule set information to the Product, and submits the rule set information for publication.

When the rule set information is published, rows are written to a number of database tables, and in particular the data from the database tables listed here will be required later, during the calculation of each case's determination result:

CREOLEProductPeriod;
CREOLEProductPeriodDispCat; and
CREOLERuleClassLink.

Important: These database tables are configured to be converted and propagated by the Entity converter and propagator respectively (see Entity Rule Objects).

The configuration is included by the application in the .../EJBServer/components/core/data/initial/blob/EntityPropagatorConfiguration.xml file.

This configuration is critical to the correct operation the Engine, and must not be modified or removed by customers.

Note that the data on the CREOLEProductDecisionDispCat database table is not required by rules processing and is not present in the configuration included in the application.

Later, during the calculation of a case's determination result, the Entity converter will populate rule object instances of these rule classes from the ProductEligibilityEntitlementRuleSet rule set:

ProductPeriod;
ProductPeriodDisplayCategory; and
RuleClassLink.

Important: The rule ProductEligibilityEntitlementRuleSet rule set provided by the application is critical to the correct operation of Cúram Eligibility and Entitlement, and must not be modified or removed by customers.