You define the format of the email.
The message body template is stored as a dataset in Teamcenter. HTML formatting allows virtually unlimited possibilities. You define the look and feel of the email message so that the proper information is communicated in a user friendly manner. Don’t send technical jargon to upper level management!
Embed object properties anywhere in the email body
Property tags can be embedded in the email template. This allows inclusion of properties from any object associated with the workflow.
Include object properties such as:
- List of workflow targets
- Form Properties
- List of reviewers
- Responsible Party
- Rejection Comments
- Task Due Date
- Instructions
Notify non-Teamcenter users
In addition to specifying a standard list of recipients, non Teamcenter users can easily be included.
A hierarchical structure can be specified so that the correct person is notified. This can be structured organizationally (the boss of the person responsible for the task), or functionally (a product manager responsible for the associated Engineering Change).
The hierarchical structure is maintained independent of the active workflow so that changes can be made as people move around within the organization.
> Content of the email is specified by designing your own templates to suit each unique type & purpose.
For example: create unique email templates for task approval notice, task rejection notice, task demotion notice, process completion notice, etc.
- Email templates are stored as text datasets in the database.
- Change email templates whenever you need without any code change, compiling or linking.
- Protect email templates by releasing them or applying access manager permissions.
- Replicate those email templates to other sites using multi-site import/export or create unique templates for other sites.
> Task or Job information to be included in the email is specified by embedding property keys directly in the template.
This allows the creation of a seamless email body when those property keys are replaced by the actual property values.
For example: inform users the task is due on a particular date, or what comments other reviewers have provided, or who/why/when they rejected the task.
- Properties can be of type attributes, references, runtime properties, compound properties, or relational properties.
- Properties can be fixed length arrays, variable length arrays, or single value.
- Properties can be of data type integer, float, double, character, string, date, boolean, or tag references.
- Properties can belong to the task, job, target objects, or any other object related to the task/job/targets.
> Send an email notification on any workflow action.
For example: send an email when targets are added/removed, when the job is promoted/demoted, or the task is approved/rejected, etc. There are no restrictions on placement of this handler.
> You decide who the recipients are.
For example: send email to (any combination of) responsible party, all reviewers, undecided reviewers, group/role/resource pool, reviewers of another review task, email addresses, Teamcenter user, distribution list, recipients specified in a target object property, change participants, or functional/organizational managerial hierarchy.
