Rule model annotations

You can add annotations that are specific to Decision Center to the rule model extension files.

You can customize the rule model extension files (.brmx and .brdx) directly in the XML files, or in the Rule Designer Rule Model Extension Editor. You can provide the following annotations in these extension files:

Table 1. Annotations and their purpose
Annotation Tag	Description
column-length	The length of the column to create in the database to store this feature. If not specified, the default value for Strings is 30.
clob	Defines whether or not you use a CLOB column to store the attribute. It can be `true` or `false`.
column-name	The name of the column in the database. You can use this annotation to provide a different name to be used in SQL to avoid any limitation of the database with regard to alias. For instance, if the name of the attribute is too long or an SQL keyword, it cannot be used as a column name. Therefore you can use this annotation to specify a different name.
validator-class	The fully qualified name of your own validator.
foreignkey-name	The name of the foreign key. For example, when an attribute is an enumeration or a hierarchy, a foreign key is created in the database between the attribute database column and the database table that contains the values for this hierarchy or enumeration. The name of this foreign key is generated automatically. However, if you have two attributes of the same enumeration or hierarchy in the class, the same foreign key name is generated for both attributes, so the script cannot be run. Consequently, use this annotation to specify different names.