G) DeterminationResult

The Determination Result (described in I) DeterminationResult) also holds the decision details for the case, as determinationDecisionDetailsTimelines. determinationDecisionDetailsTimelines is a map from each display category to a timeline of XML data (which holds the varying decision detail data for that display category).

Each product period can contribute to the XML data for a particular display category. If a product period does not have rules configured for a particular display category, then for the period of time that the product period contributes to the case's determination, the XML data will be empty and no decision details can be displayed for that period.

The Engine calculates the XML data for a product period's contribution to a display category by starting with a rule object created for that product period/display category, and then "walking" the values on that rule object to gather XML data as follows:

• The Engine walks all the displayable data to find out all the "change dates" on which any timeline values change (because the eventual overall XML will change on each of these change dates). The Engine walks the displayable data in a recursive fashion as follows:
  • Create an instance of the decision details rule class (see C) Custom rule classes for decision details);
  • Find every attribute on the rule object which is annotated with the Display annotation (other non- Display attributes are ignored).
  • For each Display attribute, processing differs according to the type of the attribute:
    • Timeline

      If the value is a timeline, then inspect the timeline value to find the dates on which it changes value, and contribute these dates to the overall change dates.

    • Rule Object

      If the value is another rule object (which has not yet been walked), then recurse to inspect its Display attributes and add their change dates to the overall change dates.

    • List

      If the value is a list of rule objects or Timelines, then each item in the list is checked to identify change dates to contribute to the overall change dates.

    • Other

      If the value type is not a Timeline, Rule Object or List then it does not contribute to the overall change dates.

• For each date on which any display data changes, the Engine creates an XML document by re-walking the data above, to find the value of each displayable item on that date (see the example below in Basic Eligibility/Entitlement example XML output). There are special cases for sub-screen data and their business object IDs to automatically include them.
• The Engine combines the XML documents for each change date into a timeline of XML documents. This timeline holds all the displayable data for a display category on the case, and the Engine stores it in the map of display categories to XML timelines.