...

If the 1st activity has an assigned role and the flow is used by a person who does not have that role, the flow will be auto-started and automatically put on the task list of the users who have that role. The person who auto-started the flow will see the pending message configured for the 1st activity. By default they will see the message "Your request is being processed". This is a useful way to start a workflow by an automated service.

Role

This field causes workflows to behave similar to role list except that the target role of the workflow is determined You can enter a comma separated list of roles in the role field, Ex: Manager, HR or use this field to dynamically determine a role at run-time. For example, you may have a workflow where the first step is a Purchase Order or a Loan Request and the second step is an approval; however the approval must be performed by a Manager if the amount is less than $1000 and a Supervisor otherwise. You can enter will need a value in this field. This field can use templatized strings for dynamic content, e.g. it can contain "{ManagerId}" where ManagerId is the name of a field in a form.  will resolve the ManagerId string using the actual value of the ManagerId control and generate a task targeted at that specific user.See the workflow example topic control in your form that is populated with the role that you want the flow to navigate to - in this case, Manager or Supervisor. To determine the role dynamically, enter the name of that control surrounded by curly braces in the Role text field for the steps in your flow that are going to use the role entered for routing e.g. {ApproveRole}. This is an example of using templatized strings for dynamic content. At runtime. Live Forms will resolve the target role using the data in the ApproveRole control and will route the workflow to that specific role. 

See the workflow example topic determining the role at run-time. A role  

A role entered in the 'Role' input box overrides the one selected in 'Role list'. This is as designed. 

User

This field causes workflows to behave similar to roles except that the target of the workflow is a specific user rather than all users with a specific role. For example, in a Vacation Request workflow, the first step is to be completed by an employee but the second (approval) step must be performed by a specific manager (person) rather than anyone with the "Manager" role. You can enter a value in this field. This field can use templatized strings for dynamic content, e.g. it can contain "{ManagerId}" where ManagerId is the name of a field in a form from a prior step.  will resolve the ManagerId string using the actual value of the ManagerId control and generate a task targeted at that specific user.

See the workflow example topic sending a workflow step to a specific user. A user id entered in 'User' input box overrides the one selected in 'Role list'. This is as designedselected in 'Role list'. This is as designed.

You can only enter a single username in this field. Ex: nancy. Setting the user property to a comma separated list of usernames, Ex: nancy, prajakta, will not work. This will be treated as a single username.

CSS Class

This CSS class name will be added to the XHTML markup generated for this step in the flow. You can use this CSS class in any CSS when customizing themes.

...

To Skip an Activity if a Control Contains a Value.

In this example if the Supervisor was the one to fill the fills in the first step of the flow then they were required to enter their SupervisorTitle, and that . The SupervisorTitle field is thus guaranteed to have a value. In this case to skip the next step by adding , add this to the second activity's precondition.

...

The email wizard lets you set your own email subject and message. The message body can contain HTML and CSS, giving you the ability to generate nicely formatted emails. Form data values can be added to the message subject and body using control template names. Two dropdowns in the wizard make it easy to add control templates. The special template {task.list.url} can be used in the email body to generate a clickable link to the user's task list. If you are using the  space feature  Space feature it is more likely you might want to return to the user's task list in the space. To do this - modify the task notification email  to use a space specific URL. It is highly recommended for forms embedded in a space,  you that you change the default Task List special template to a space specific URL which will return you to the user's Task List embedded in your chosen space. Create a space specific URL by supplying a URL to the Task List with the space/spaceID/tasklist appended to it: 

...

Normally, when you click Save to save a partially completed flow, the saved flow will only appear on your own task list. If you check this box, then the saved flow is assigned to the user that is specified in the Users property. When you use this feature the User property should contain a template. For example, you may have form that needs to be reviewed and approved in an ad-hoc manner. See the flow example Ad-hoc workflow: pass activities between arbitrary users for a deeper understanding of this feature. In this manner, you can create a step in a flow that loops several times and that dynamically routes to different people before continuing.

Remember, you cannot select "Save to User" if Quick View is enabled.

1.