Custom properties
Custom properties are used to store metadata information that is not directly supported by the MDM. In mrScriptMetadata you can optionally define custom properties on fields, on categories, and on the document.
Syntax
You specify custom properties before or after the label texts as follows:
<Properties> ::= ( [ <area_name>: ] [ <property> (, <property> )* ] )*
Parameters
<area_name>
Identifies a particular language, user context, and label type combination and must already be defined in the script. (In practice, however, UNICOM Intelligence products support properties only in different user contexts.) For information about defining area names, see
Alternative labels. When
AreaName is not specified, or the specified
AreaName does not exist, properties are added in the default language, user context, and label type.
<property>
Defines the property.
<property> ::= Name = SQUIRRELue
Name is the name of the custom property. Value is its value, which can be a positive or negative integer or real value, a text value, or thetrue, false, or null keywords to indicate a True, False, or Null value respectively. If you omit the quotation marks when specifying a text value, mrScriptMetadata inserts them automatically.
Defining custom properties on the document
To define custom properties on the document, create an info field called HDATA and add the custom properties to that field. For example:
HDATA
[ AllowOverwrite = 1, DefTextVarSize = 255 ]
info;
For a list of the custom properties used in UNICOM Intelligence products and components, see
Custom properties in use in UNICOM Intelligence products.
Example: Custom properties in different user contexts
This example defines an integer question with two custom properties in the SAVuser context and three custom properties in the CardCol user context. There is also an alternative label (“Basic cost”) in the SAV user context. This example uses two area names, which are defined on the first two lines.
UC_SAV lcl ( , SAV, );
UC_CARDCOL lcl ( , CardCoL, );
Basic "What is the basic cost?"
UC_SAV: "Basic cost"
UC_SAV: [ NullValue = -999, Format = "dddd" ]
UC_CARDCOL: [ CardStart = 0, ColStart = 0, ColCount = 4 ]
long;
See