Using substitution variables in message and subject text

Email message and subject text can be constants that contain variables.

A Role_Email collaboration object substitutes data from the processing state or business object into these variables dynamically. For instance, in the message
An item with GTIN ${item.catalogueItem.tradeItem.itemInformation.   \
tradeItemIdentification.gtin} was approved and synchronized to the back end system
the GTIN value represented by ${item.catalogueItem.tradeItem. itemInformation.tradeItemIdentification.gtin}
${item.catalogueItem.tradeItem. itemInformation.tradeItemIdentification.gtin}
is filled in automatically during the generation of this message.
Variables to be substituted must be enclosed in prefix and suffix characters. The substitution variable characters are defined in the values of the Role_Email collaboration object's configuration properties SUBSTITUTION_VARIABLE_PREFIX and SUBSTITUTION_VARIABLE_SUFFIX. In the following example, these properties are set as follows:
SUBSTITUTION_VARIABLE_PREFIX = ${
SUBSTITUTION_VARIABLE_SUFFIX = }
As a result, the substitution variables in the email message and subject text must appear as: ${variable_name}
Note: These characters might have to be changed to meet National Language requirements.

Supported values

The supported values for variable_name, along with the values that the collaboration object actually inserts in the text, are as follows:
ROOT The entire triggering business object.
Date The current date
getName The name of the triggering business object
getVerb The verb of the triggering business object
Any attribute name The value of the named attribute from the triggering business object. If the value for variable_name does not match one of the specific values above, the collaboration object interprets it as the name of a business object attribute.

Parent topic: Controlling e-mail