Difference between revisions of "Workflow Task Type: Select User for Next Task"

From SmartWiki
Jump to: navigation, search
(Task Settings)
Line 16: Line 16:
  
 
{{WorkflowTaskTypeMessageTemplate}}
 
{{WorkflowTaskTypeMessageTemplate}}
 +
{{WorkflowTaskTypeRouting}}
 +
{{WorkflowTaskRoutingOptions}}
  
 
==See Also==
 
==See Also==

Revision as of 09:34, 27 September 2013

This task type used to allow the current user to pre-select the user that is responsible for the task that immediately follows this task type.

  • This is necessary for tasks that will trigger at a later date.

For example, consider a Workflow that is triggered on the status of Escalated which is configured to send a reminder e-mail to a manager if the status has not changed for seven days. If the reminder e-mail workflow task has Let current user select target user from this role as the recipient the Workflow would fail. This is because the e-mail is triggered (seven days later) by the system, and there is no current user.

WorkflowTaskTypeSettings-SelectUser.png

Task Settings

Request for Approval Tasks have the following settings:

  • Name - Narrative name for the task.
  • Task Number - A system generated number that determines the presentation order of the task in the workflow. This number can be changed to display the step in a different location.
  • Description - Detailed description of the task (optional).
  • Expire After - Intended duration of the workflow.

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). Additional Email Syntax options can be used within this field.
  • 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 - will create an e-mail activity. If its L1/L2 workflow, where the UTA L2/L3 Email Activity settings have been configured, then the it will be saved as L2/L3 event under the L1/L2 object. Otherwise it will be saved as user event against each recipient in the To field.

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.

See Also