Properties are different for each part and for each stereotype; when you create a part, check to see what properties are appropriate. Some parts have required properties, but most properties are optional.
DataItem cost money(10,2) {Currency = yes, CurrencySymbol = "$"} endThe code block that begins with the opening brace and ends with the closing brace (that is, the list of properties and their values) is referred to as a set-value block.
Properties are useful only in specific situations. For example, DataItem parts can include properties that apply only to specific types of user interfaces. As in the previous example, you can specify the properties currency and currencySymbol on any DataItem part to indicate that the DataItem represents a currency value and to specify the monetary symbol used in displaying the value.
You must provide a valid value for each property. Some properties accept string literals, some accept a "yes" or "no" value, some accept values from lists of options called enumerations, and others accept array literals. In most cases, you cannot use a variable or constant as the value of a property. In other words, you cannot use a Boolean variable or a string variable set to "yes" or "no" for the value of the currency property; you must specify a literal, unquoted "yes" or "no" value.
Some properties are provided for compatibility with previous versions or migrated code and are unnecessary for new EGL applications. To know which properties are provided for new code and which are used for compatibility, see the topic in the Reference section that covers a particular part and its properties.
DataItem myRedVar int {color = red} end Record myRedRecord type BasicRecord myField myRedVar; endIn this example, the field myField functions as though you specified the color property on it.
myRedInt int {color = red}; myBlueInt int {color = blue}; myBlueInt = myRedInt;In this example, myBlueInt still has the color property set to blue.
Reference variables are an exception to property transfers. For more information, see "Properties" in the Reference section.
DataItem myRedVar int {color = red} end Record myBlueRecord type BasicRecord myField myRedVar {color = blue}; endIn this example, the myField field overrides the red value with the blue value.
myBlueVar int {color = red, color = blue};In this example, the color property of the variable is set to blue because the second definition overrides the first.