Workflow Manager 2016
Workflow Manager comes with a set of default email templates, which are used to determine the design and content of Workflow Manager’s notification email. There are two basic types of email templates:
| • | System email templates—For some notification events—such as when a new issue is created or when a workflow request’s status is changed—Workflow Manager will always use the same email template. However, you can edit these system templates in the Email Template Administration interface to customize them for your organization. |
Note • For these system events, Workflow Manager will always use the email template that is specified for that event in the web.config file (as described in Specifying the Default Email Templates for Email Notifications).
| • | Workflow step email templates—When defining a workflow step on the Workflow Step Details view, you are prompted to specify an email template to use when that step is initiated, rolled back, edited, and completed. A default email template is specified for each of these four events. However, you can create additional “workflow step” email templates, which will then be available for selection on the Workflow Step Details view. |
The following table describes Workflow Manager’s 16 default email templates:
|
Category |
Template Name |
Description |
|
System templates |
ApplicationStatusChanged.txt |
Sent when the Status of a workflow request has changed, such as from Active to Inactive. |
|
ApprovalTask.txt |
Sent when a workflow step with a Step Type of Approval Task is initiated. The email recipient can either approve or reject this workflow step directly from this email—without being required to open the Workflow Request page of Workflow Manager—by clicking the Approve or Reject link. |
|
|
DataChanged.txt |
Sent when someone edits a workflow request’s previously submitted (and accepted) data. |
|
|
DataChangedNewRequest.txt |
Sent when someone submits data for a new workflow request. |
|
|
IssueCreation.txt |
Sent when a new issue has been created for a workflow request. |
|
|
IssueResponse.txt |
Sent when a workflow request’s existing issue has been responded to. |
|
|
NewSLABreakage.txt |
Sent when a workflow request is past due the due date defined in the Service Level Agreement (SLA). |
|
|
NewSLARisk.txt |
Sent when a workflow request is at risk of exceeding the due date defined in the Service Level Agreement (SLA). |
|
|
StepLevelSLAAtRisk.txt |
Sent when a workflow step is at risk of exceeding the due date defined in the Service Level Agreement (SLA). |
|
|
StepLevelSLABreakage.txt |
Sent when a workflow step is past due the due date defined in the Service Level Agreement (SLA). |
|
|
NormalStep.txt |
Sent to assigned user assigned to a Normal step to enable them to advance the workflow the next workflow step by clicking the Advance Workflow button in this email. |
|
|
UpdateHistory.txt |
Sent to assigned user assigned to an Update History step to enable them to advance the workflow the next workflow step by clicking the Advance Workflow button in this email. |
|
|
Workflow step templates |
WFAdvanced.txt |
Default email template to send when a workflow step is advanced. |
|
WFCompleted.txt |
Default email template to send when a workflow step is completed. |
|
|
WFRollback.txt |
Default email template to send when a workflow step is rolled back. |
|
|
WFStepEdit.txt |
Default email template to send when a workflow step is edited. |
See Also
Workflow Manager 2016 / AdminStudio Enterprise Server 2016 Help Library12 July 2016 |
Copyright Information | Flexera Software |