An Email
is designed to be used in the composition and delivery of mail messages. An
Email may specify five directly contained
Values,
all of which must be type
string
.
If the following Email
attributes are defined as Values,
they may be set at runtime to programmatically control the sender, recipient
or subject of the Email:
An Email contains the Operation send, which will attempt to deliver the current Email instance as described by BuiltinOperation. When an Email is composed, the body of the Email will be composed of all contained Values and their values at the time the Email was sent. The format of this body may use a custom template if this template is specified.
An Email contains the Events onSent and onFailure. These events are triggered once an Email has been successfully delivered and when an Email is unsuccessfully received, as discussed in Event.
An IAML model instance may contain any number of Emails. The storage semantics for a Email follow the storage semantics for its containing scope, similar to the storage semantics for the Frame element.
[Email.html]CUSTOM_ROOT/templates/ id.php
isreadable at runtime, this template file will be used to render the Email insteadof
the default template. [testCustomTemplate()]
@example
will instantly fail;
it will not even attempt to be sent.
[Definitions]
templates/ID.php
; otherwise,
a default builtin template is generated.
[Definitions]
true
if the current element has been generated.