The conversion of business data into CER rule objects supports the use of the majority of the application's fundamental domain types.
The table below shows the correct CER data type to use for a CER rule attribute, which at rule object conversion time will be populated from a database or evidence field based on a domain. The table also describes any logic which is applied at data conversion time and the default value that the rule object converters will use for any values which are not sourced directly from data sources (e.g. when populating before-start or after-end values in a timeline):
Cúram Domain Type |
CER Rule Attribute Type |
Data conversion logic |
Default value |
---|---|---|---|
Numerical types:
|
Java class - Number |
Converted to CER's own numerical format. |
0 |
Character types:
|
|
An empty String (""). |
|
SVR_BLOB |
Not supported. |
||
SVR_BOOLEAN |
Java class - Boolean |
false |
|
SVR_DATE |
Java class - curam.util.value.Date |
The "zero date" (blank) is converted to a null value. |
null |
SVR_DATETIME |
Java class - curam.util.value.DateTime |
The "zero date time" (blank) is converted to a null value. |
null |
Rule attributes of this curam.creole.value.Message data type do not map to a domain type, and so cannot be populated by the rule object converter. Any data named "description" in the source data will be ignored.