...

This is an important consideration when migrating forms to version 5.1.1. See this documentation for more information.

Description

By default all flow descriptions say, “Edit the flow to change this description,” but you can change this if you wish. The description appears as a tool tip when you mouse over the area just to the right of the flow's share  icon on the Flows home page. You also see this description when you view individual submission documents.

...

When you save a partially filled flow to continue it later or when  puts a task on your task list as part of a workflow, the task is accessed via your task list. This field controls the name that gets displayed in the user's task list. For more details, see the Tasks documentation. This field can use templatized strings  for dynamic content, e.g. the Task Info can contain "Vacation Request for {FirstName} {LastName}" where FirstName and LastName are the names of fields in a form from a prior step in the flow. Before putting the task on a user's task list,  will resolve the Task Info string using the actual values of the FirstName and LastName fields e.g. "Vacation Request for Tom Smith".  will truncate the Task Info data to 250 characters.

You access your Task List from your applications home page. You use the Task list to to perform tasks assigned to you, to view a task's history, or search for tasks you've participated in — a tenant admin can also search for other users' tasks.

...

This field is a toggle that sets the state of your flow to production or development. Functionality is the same as Deployment for forms. 

Setup Key/Saved/Summary

...

Fields 

This setting controls which fields are saved to the built-in submissions repository. By default, all your data is saved as an XML document. This is the most efficient way to store/access your data both in terms of speed as well as storage. However, if you prefer to view your data via  via the submissions user interface, you can choose which fields are saved in addition to the XML data. Note that this could incur significant performance overhead and will also consume additional storage in the repository.

Considerations when deciding which types of fields to configure are listed below.

• Key fields are indexed for easy search of Submissions. You will see the controls designated as Key fields in the Submissions table. This is helpful when trying to locate a particular submission from a long list. Key fields do not affect performance. They are not downloaded when exporting your submissions to Excel.
• Saved fields do affect performance as they are independently stored in addition to XML data. This can significantly reduce performance, especially for large forms and require additional storage in the repository. Saved fields are not rendered in the submission table and cannot be used as search criteria for submissions. Saved fields  are downloaded to Excel.

Clicking on the link displays a wizard. The wizard will display the fields from your flow. Key and Saved fields have the same meaning for flows as for forms. Please refer to the Setup Key/Saved Fields documentation for forms for details on these fields.

...