Changes

:::* '''Name''' - Narrative name for the task.:::* '''Task Type''' - manually set to Create Consumer/Provider Link:::* '''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.:::* '''Web Page Field ID''' - Must contain the Custom Field ID of the Web Page View to be converted into PDF format. To create multiple PDFs, enter the Custom Field IDs of the Web Page View fields in the Web Page Field ID# setting of the Workflow Task, separated by commas.:::* '''Store to Field ID''' - If PDF file should also be stored to the record, must contain the Custom Field ID of the relevant Link - Multiple Files custom field.:::* '''PDF Render Language''' - If a language is specified, the language option will be applied to the PDF generated

:::* '''Message Template: 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@):::* '''Message Template: CC Email Address''' - CC recipients address. (Separate multiple addresses with commas). Additional Email Syntax options can be used within this field.:::* '''Message Template: Email Body Format''' - Options are Plain Text or HTML.:::* '''Message Template: 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}Template:::** Importance={high,normal,lowWorkflowMessageTemplate}:::** Sensitivity={personal,private,company,confidential}:::**: e.g. Priority=urgent;Importance=high:::* '''Message Template: Subject''' - Narrative subject line of the message.:::* '''Message Template: Body''' - Narrative body of the message.:::* '''Message Template: 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.:::* '''Message Template: Attachment File IDs''' - Attach additional default files when triggered from a Smart Folder. See the Determining the File ID article for instructions.:::* '''Message Template: Save as Event''' - will create an e-mail activity. If it’s L1/L2 workflow, where the UTA L2/L3 Email Activity settings have been configured, then it will be saved as L2/L3 event under the L1/L2 object. Otherwise it will be saved as user event against each recipient.:::* '''Routing: Use Variable for Recipients''' - Allows recipients of the message to be selected using variables. See this article for configuration details.:::* '''Routing: Use UTA Role''' - When using roles to select recipients, the UTA Role can be used to determine recipients.:::* '''Routing: Role''' - Used to select recipients by role.:::* '''Routing: 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: 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.