EmailTemplate Nested Elements
The components listed are generally expressed as nested elements due to their complexity and length.
<subject>
Subject line for the email message
<body>
Body, or main content, of the email message
<signature>
Hashmap of arguments to the email template
The signature for each template cannot be changed through the XML. Arguments to each template vary based on the associated system activity to which they apply. Properties and methods belonging to any object passed as an argument are available to include in the message, but other objects that are not part of the template signature cannot be retrieved to use in the email message.
<Inputs>
Nested element within Signature, signifying the input arguments to the template
<Argument>
HTML cannot be passed into a template as an argument value. All HTML must be included as part of the base template.
Nested element within Signature and Inputs. This element names and specifies the type of each input argument to the template
<Description>
Indicates descriptive information for the reader of the XML. Describes the element in which it is nested
For example:<Description> within <Argument> describes the argument usage.<Description> within the <EmailTemplate> describes the purpose and usage of the template
At the most basic level, the contents of these elements and attributes can be written as straight text values with no variable substitutions. However, the real flexibility and usefulness of these templates is found when custom text is substituted into the message body, subject, and other attributes. This substitution is managed by the Apache Velocity Engine.