Output markup expressions can include variables. Variables can point to values of simple types like integer, double, date&time etc., can point to markup classes with properties or can point to a collection o other markup variables.
In markup expressions variables of simple type are referenced by their name, the properties of an object are referenced by <variablename>.<propertyname>, members of a collection are referenced by their index. See Table2 for examples.
Markup expression |
Result |
{{VariableA}} |
If VariableA points to a simple type this expression will be replaced by the value of the simple type. If VariableA points to a class the expression will be replaced by a textual representation of all properties of that class. If VariableA points to a collection this expression will be replaced by an empty string |
{{VariableB.Property1}} |
If VariableB points to a class and that class has a property of a simple type named Property1 the expression will be replaced by a textual representation that property. If VariableB points to a class and that class has a property of named Property1 that is itself a class the expression will be replaced by a textual representation of all properties of that class. |
{{VariableC[0].Property1}} |
If VariableC points to a collection and members of that collection have a property named Property1 this expression will be replaced by the value of Property1 of the first element in the collection. Note that the collection index is zero-based. |
Table 2: Examples for the usage of markup variables.
Names of variables and properties are case sensitive.
There is a set of common variables available in every text template, see chapter Common markup variables for a complete listing of those variables. The context in which a template is executed may define more variables. Refer tot he documentation of the context for details.
