Difference between revisions of "Template:WorkflowTaskTypeMessageTemplate"
From SmartWiki
(Created page with '===Message Template=== * '''Message Type''' - Type of message – e-mail, instant message, both, or none required with this task. E-mail and instant messages can be created usin…') |
|||
| Line 15: | Line 15: | ||
* '''Attachment File IDs''' - Attach additional default files when triggered from a [[Smart Folder]]. See the [[File ID|Determining the File ID]] article for instructions. | * '''Attachment File IDs''' - Attach additional default files when triggered from a [[Smart Folder]]. See the [[File ID|Determining the File ID]] article for instructions. | ||
* '''Save as Event''' - Email will be saved as an event. | * '''Save as Event''' - Email will be saved as an event. | ||
| + | |||
| + | ===Routing=== | ||
| + | * '''Use Variable for Recipients''' - Allows recipients of the message to be selected using variables. See [[Using variable syntax to select recipients for workflow tasks|this article]] for configuration details. | ||
| + | * '''Use UTA Role''' - When using roles to select recipients, the [[UTA Role]] can be used to determine recipients. | ||
| + | * '''Role''' - Used to select recipients by role. | ||
| + | * '''Selected Users''' - If required, specific [[User|users]] can be selected to complete this task. This technique restricts the number of [[User|users]] that the initiator can select. | ||
| + | * '''Routing Options''' - Specifies the types of options available to process this [[Workflow|workflow]] step. In many instances, the default options can be used, such as Approved, Rejected or Revise. But additional and alternate sets of options can be created to reflect more complex business processes. | ||
Revision as of 15:46, 23 September 2013
Message Template
- Message Type - Type of message – e-mail, instant message, both, or none required with this task. E-mail and instant messages can be created using variables that will create custom messages specific to instances of the workflow. Options are No Message Required (default), Quick Message, Email Only and Quick Message and Email.
- From Address - Email address sent from. This field accepts variables, so you can either hard-code a value (i.e. donotreply@mycompany.com) or use variable syntax (i.e., on a Level 1 Workflow, @owner.email@)
- CC Email Address - CC recipients address. (Separate multiple addresses with commas)
- Email Body Format - Options are Plain Text or HTML.
- Email Message Header - The email header can be modified using the following syntax, with the arguments separated by semicolon:
- X-Priority={1,2,3,4,5}
- Priority={normal,urgent,non-urgent}
- Importance={high,normal,low}
- Sensitivity={personal,private,company,confidential}
e.g. Priority=urgent;Importance=high
- Subject - Narrative subject line of the message.
- Body - Narrative body of the message.
- Attach Object - Attaches the details of the object to the message. In the case of a SmartSimple object, such as a company, person, or application, the textual details of the object will be added. If the object is a file, then the file will be attached to an e-mail message, but not an instant message.
- Attachment File IDs - Attach additional default files when triggered from a Smart Folder. See the Determining the File ID article for instructions.
- Save as Event - Email will be saved as an event.
Routing
- Use Variable for Recipients - Allows recipients of the message to be selected using variables. See this article for configuration details.
- Use UTA Role - When using roles to select recipients, the UTA Role can be used to determine recipients.
- Role - Used to select recipients by role.
- Selected Users - If required, specific users can be selected to complete this task. This technique restricts the number of users that the initiator can select.
- Routing Options - Specifies the types of options available to process this workflow step. In many instances, the default options can be used, such as Approved, Rejected or Revise. But additional and alternate sets of options can be created to reflect more complex business processes.
