Concepts > Attributes (MetaAttributes) > Mail Body
Mail Body
This property allows to define the template which will generate the message body.
 
To configure your template you can mix some text and the following tags.
Tags are replaced in your text by values and are explained below.
 
Template example : "My workflow is : [@WorkflowName@]."
Result : "My workflow is : Validation."
 
 
Tags :
 
- [@TaggedValue=<TaggedValue
Generates the value of the given TaggedValue entered when the Transition was triggered.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
 
- [@Comment,Transition=<Workflow Transition
Generates the value of the comment entered when the Transition was triggered.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
 
- [@TransitionName=<Workflow Transition
Generates the name of the triggered Transition.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
 
- [@StatusName,Transition=<Workflow Transition
Generates the name of the Status following the triggered Transition.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
 
- [@StatusInstanceName,Transition=<Workflow Transition
Generates the name of the StatusInstance created by the triggered Transition.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
 
- [@Activator,Transition=<Workflow Transition
Generates the name of the User who triggered the Transition.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
 
- [@Date,Transition=<Workflow Transition
Generates the date and time when the Transition was triggered.
The transition can be omitted. In this case it matches the current triggered transition.
If the transition is specified it identifies the last matching transition already triggered.
Here is a sample of Format: "yyyy/MM/dd HH:mm:ss UTC".
 
- [@WorkflowName@]
Generates the name of the workflow definition matching the executed workflow.
 
- [@WorkflowInstanceName@]
Generates the name of the executed workflow.
 
- [@WorkflowSubjectProperty=<"MegaField"|PropertyId
Generates the given property value of the workflow subject.
Use "MegaField" to generate the workflow subject MegaField.
Use a MetaAttribute identifier to generate the matching value.
Example : [@WorkflowSubjectProperty=MegaField@]
Example : [@WorkflowSubjectProperty=Name@]
 
- [@Macro=<Macro
Generates a text returned from a function implemented in the given macro.
The identified macro must contain a Function that matches the following signature:
* Function <FunctionName
 
 
- [@BeginAllTaggedValues@] ... [@EndAllTaggedValues@]
Generates the text included between those tags for each TaggedValue of the currently triggered Transition.
The specific following tag can be used in the included text to generate some information relative to the TaggedValue:
[@TaggedValueProperty=<"Name"|"Value"
Use "Name" to generate the TaggedValue name.
Use "Value" to generate the TaggedValue value.
Example :
| Properties :
| [@BeginAllTaggedValues@] - [@TaggedValueProperty=Name@] : [@TaggedValueProperty=Value@]
| [@EndAllTaggedValues@]
 
- [@BeginAllAttachedObjects,Attachment=<AttachmentMotive1
Generates the text included between those tags for each object attached when the current Transition was triggered.
The specific following tag can be used in the included text to generate some information relative to the attached object:
[@AttachedObjectProperty=<"MegaField"|PropertyId
Use "MegaField" to generate the attached object MegaField.
Use a MetaAttribute identifier to generate the matching value.
You can use "Motives" to filter objects attached to specific attachment motives.
Example1 :
| [@BeginAllAttachedObjects@]
| [@AttachedObjectProperty=MegaField@]
| [@EndAllAttachedObjects@]
Example2 :
| [@BeginAllAttachedObjects,Attachment=Attachment1 Attachment2@]
| [@AttachedObjectProperty=Name@]
| [@EndAllAttachedObjects@]
 
- [@BeginAllNextTransitions@] ... [@EndAllNextTransitions@]
Generates the text included between those tags for each next transition following the current Status (following the current triggered Transition).
The specific following tag can be used in the included text to generates some information relative to Transition :
[@NextTransitionProperty=<"MegaField"|PropertyId
Use "MegaField" to generate the Transition MegaField.
Use a MetaAttribute identifier to generate the matching value.
Example : [@NextTransitionProperty=MegaField@]
Example : [@NextTransitionProperty=Name@]
 
- [@Url,IdAbs=<Object Field
Generates the text of a "Link". This link allows you to access an object from the e-mail.
* Object: You can choose an object with <Object Field
"Query" relates to the subject or to the Root (if no subject).
For "Macro" you must implement the function "getUrlObject(WorkflowContextAction)" that returns the object.
* Tool: You can choose a Tool to 'open' your object. Two tools are available: "PropertyPage" and "Document".
If your tool is "Propertypage" you can specify a simple Propertypage (with PropertyPage=..). By default all PropertyPages are shown. You can complete your description with the "Parameter" tag.
If your tool is "Document" then no specification is needed.
If you want to define your specific tool, you can use "Parameter" to describe Tool, Param, ParamValue and ParamValueMetaClass. <Value
If you use the "Parameter" tag you must put this at the end of parameterization text.
* Database: you can specify another repository. By default it is the current repository. If this tag is empty, the user must choose a repository.
* Environment: you can specify another environment. By default it is the current environment. If this tag is empty, the user must choose an environment.
* Application: you can specify another Mega Application. By default it is the current web application. If this tag is empty, the user must choose an application.
* Desktop: you can specify another Desktop. By default it is the current web desktop. If this tag is empty, the user must choose a desktop. A Desktop must be used by an Application.
* Name: You can choose a Name for your Link. By default no name is defined.
* Profile: You can choose a Profile for your Link. By default no Profile is defined.
* Role: You can choose a Role for your Link. By default no Role is defined.
* Affinity : you can choose a specific "Desktop Container Affinity".
Sample:
[@Url,IdAbs=Object1@]
[@Url,IdAbs=Object1,Tool=PropertyPage@]
[@Url,IdAbs=Object1,Tool=PropertyPage,PropertyPage=MetaPropertyPage1,Parameter=,Affinity=Affinity1@] 'In this sample, value of "Parameter" is ",Affinity=Affinity1"
[@Url,Query=Query1,Name=MetaAttribute1@]
[@Url,Macro=Macro1,Name=CodeTemplate1@]
[@Url,Subject@]
[@Url,Subject,Environment=C:\Program Files\Mega\Env1,Parameter=Tool=Sj(3hVHpEXUN,Param=VHRbsTkZFLvH,ParamValue=<Value
[@Url,Application=The Web Front-end,Desktop=Teamwork@]
Translations
Type
VarChar (4) Standard
 
List of MetaClasses