...

This is the name you see on the Flows home page where your flows are listed. We recommend changing the name to make it more meaningful than the arbitrary name assigned when you create it, but keep in mind it is a working name only, so users will not see it. It is recommended that you name your form/flows using characters that are suitable for filenames. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works.

Element Name

There is a now a The flow property called , Element Name. By default, this is set by default to form for newly created forms as well as flows. The root element name of the from-scratch document is determined by what you put in here. It needs to be a valid XML element name. The designer can now change the name of the flow without impacting the element name.

...

The default value for Navigation is Navigation toolbar. When you configure the Navigation toolbar for your workflow, users will see the following:

• The the name of the current step displays with a bright blue color. Note that the active step number is also circled in bright blue. Steps that have yet to be performed display with a faded light blue color.
  
  
  
  
• HTTP Wait-Notify and Anonymous Email steps, once performed, display with a faded blue color indicating that the flow cannot be reset to this step.
• Skipped steps display with a faded light blue color and steps that have already been performed display with a black color. For example the Expense Report workflow shown in the image, has four steps: Expenses, Reviewer, Supervisor and Accounting. The employee fills out the Expense report for an amount less than $5000.00. The flow is routed to a company reviewer and if approved, to Accounting for final processing. . If the amount of the expense had been greater than $5000.00 then the flow is routed to a Supervisor for an additional review before navigating to the Accounting department. The Supervisor step is skipped for Expense reports less than $5000.00. When the Accounting employee performs the task, here is what they will see:

...

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 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 choose which fields are saved in addition to the XML data.

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.

...

Imagine you are entering data into a large screenflow and something happens that causes you to navigate away from the flow.. you just lost all your work!. Checking the Save on Navigate property, saves the task to your Task List. Users can go to their Task List to retrieve the task and they will  be returned to the screen where they were when the browser was closed. For example, let's say you have a screenflow with steps A > B> C and the user closes the browser at screen B. When the user performs the task from the Task List, the flow will open up at step B.

Here is a short synopsis of when the current location is saved. Consider a flow with the following steps/roles: Role1(A → B → C) → Role2(D) → Role3(E):

...

The Fast Finish feature is very useful when you're filling a lengthy screen flow.  workflows consist of steps (steps) performed by the same person or more than one person. Steps in a workflow performed by the same person are called multipage forms or screen flows. The  The designer can select the Navigation Toolbar  or add a Summary step as one of the steps to provide an easy way to move forward and backwards through the steps of a  workflow. 

Let's say a user needed to return to a previous workflow step to change entered data. The user clicks the step on the Navigation toolbar or the edit link in a Summary step and the flow returns to the previous step so the user can make the change. In previous versions, once the change is made, the user would have to click to click through all of the remaining screen flow steps in order to resubmit the flow with the updated data.

The Fast Finish feature provides a finish button, visible in use mode, in addition to the Submit and Save button (if Save/Load  is selected) for the forms in your flow. The Finish button works the same way as the Continue button. The flow will not advance to the next step or be submitted If any of the fields are invalid. 

...

1. An step is encountered that is not valid - this could be as simple as a required field that was not filled in.
2. The next task is assigned to another any user/role that is different or the same from the user that selected finish - an example would be the step in the workflow that gets routed to a manager for approval.
3. The next task is an anonymous Email or HTTP step type.
4. The last step is valid and submitted.

...

See Force Auth described in designing forms.

Accessible

Live Forms can be used to build accessible forms/flows that meet Section 508 and WCAG 2.0 accessibility standards. Check the Accessible property to turn on this feature. Refer to this documentation for the details.

Decorated

Decorated is checked by default when you create a new flow. If  you uncheck Decorated at the flow level, newly added controls in the forms of your flow will not have a decorator. Controls in the forms that already have decorators will retain them. The designer can select a decorator for each of the steps in a flow that will display on the navigation bar.

...