Write the Dynamic UIM screens

For each top-level screen and sub-screen, you must write a Dynamic UIM file and associated .properties file, and then store these files on the database.

Top-level screens

For each top-level screen, write UIM including the following:

Accept these page parameters:

<PAGE_PARAMETER NAME="determinationID"/>
<PAGE_PARAMETER NAME="displayDate"/>

Call the standard interface to retrieve XML data for a display category for a coverage period, and connect the parameters required by the call:

<SERVER_INTERFACE
  CLASS="CaseDetermination"
  NAME="DISPLAY"
  OPERATION="viewDecisionDisplayRulesCategoryXML"
/>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="determinationID"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$determinationID"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="displayDate"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$date"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="TEXT"
    PROPERTY="CategoryRef"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$categoryRef"
  />
</CONNECT>

Decide on a "category reference" for your display category (which will be used later when configuration your product's display categories). Create a .properties entry for the CategoryRef of the display category:
```
CategoryRef=MY_CATEGORY_REF
```

If your top-level screen requires data from the previous decision period to compare to, then write a call to perform additional retrievals and connect the parameters:

<SERVER_INTERFACE
  CLASS="CaseDetermination"
  NAME="DISPLAY_PREV"
  OPERATION="viewPreviousDecisionDisplayRulesCategoryXML"
/>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="determinationID"
  />
  <TARGET
    NAME="DISPLAY_PREV"
    PROPERTY="key$determinationID"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="displayDate"
  />
  <TARGET
    NAME="DISPLAY_PREV"
    PROPERTY="key$date"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="TEXT"
    PROPERTY="CategoryRef"
  />
  <TARGET
    NAME="DISPLAY_PREV"
    PROPERTY="key$categoryRef"
  />
</CONNECT>

Write custom UIM to query the xmlData returned from the server call(s) via XPath-like expressions, and lay out this data on the screen. (This step is typically where the bulk of your screen implementation effort will lie.)
If the screen allows the expansion of rows to show sub-screens, write UIM to connect to your sub-screen.

See the screen CREOLEDisplayRules_basicCaseDisplay.uim included with the Engine for a full example of a decision details top-level screen (including connection to a sub-screen).

Sub-Screens

For each sub-screen, write UIM including the following:

Accept these page parameters:

<PAGE_PARAMETER NAME="determinationID"/>
<PAGE_PARAMETER NAME="displayDate"/>
<PAGE_PARAMETER NAME="businessObjectID"/>

Call the standard interface to retrieve XML data for a business object within a display category for a coverage period, and connect the parameters required by the call:

<SERVER_INTERFACE
  CLASS="CaseDetermination"
  NAME="DISPLAY"
  OPERATION="viewDecisionDisplayRuleCategorySubscreenXML"
/>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="determinationID"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$determinationID"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="displayDate"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$date"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="TEXT"
    PROPERTY="CategoryRef"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$categoryRef"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="PAGE"
    PROPERTY="businessObjectID"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$businessObjectID"
  />
</CONNECT>
<CONNECT>
  <SOURCE
    NAME="TEXT"
    PROPERTY="SubscreenName"
  />
  <TARGET
    NAME="DISPLAY"
    PROPERTY="key$subscreenName"
  />
</CONNECT>

Create a .properties entry for the CategoryRef of the display category, and the SubscreenName (which is the name of the attribute on the case rule object which is annotated with DisplaySubscreen):
```
CategoryRef=MY_CATEGORY_REF
SubscreenName=myCaseRuleAttributeWithDisplaySubscreenAnnotation
```
Write custom UIM to query the xmlData returned from the server call via XPath-like expressions, and lay out this data on the screen. (This step is typically where the bulk of your screen implementation effort will lie.)
If the screen allows the expansion of rows to show further sub-screens, write UIM to connect to your sub-screen.

See the screen CREOLEDisplayRules_basicCaseDisplay_objectiveTagSubscreen.uim included with the Engine for a full example of a decision details sub-screen.

Storing your screens

Refer to the Cúram Web Client Reference Manual for more details.