::* '''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.::* '''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}::** Importance={high,normal,low}::** 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.