...

Flow Name

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.

...

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 flow is instantiated and step A is rendered: does not save because it is the FIRST step (if the user abandons the flow in the browser it is as if it never existed).
• The user clicks next: saves BEFORE step B renders.
• The user clicks next: does not save because the role change will do a save to the db in the PENDING state.
• Role2 performs the task: no need to save here since the flow is already saved in the db in the PENDING state.
• Role2 clicks continue: saves before the step is rendered.
• will not save if the step is READONLY - this might be the case if the user navigates back to a previous step that was performed by a different user.
• will not save when the flow navigates from an HTTP/Email step to the next one.
• will not save when the flow is completed.

Screenflows consisting of an Email step followed by multiple sequential steps that are performed by an anonymous user bring the user back to the flow at the current/latest anonymous step if the Save on Navigate feature is selected.

Configuring Save on Navigation

This feature can also be turned on globally, If configured on a server level, it will apply to all workflows. You must modify configuration parameters to turn on this feature. If you want to save workflow steps that are partially filled in to the Task List, enable the Save/Load feature in your workflow. 

Show in History

If this checkbox is unchecked, tasks for the form or flow will not appear in Task History searches. If you want them to appear, make sure this box is checked. Checking or Un-checking it affects all tasks including ones that were created prior to the action.  

Task for First Step

• no need to save here since the flow is already saved in the db in the PENDING state.
• Role2 clicks continue: saves before the step is rendered.
• will not save if the step is READONLY - this might be the case if the user navigates back to a previous step that was performed by a different user.
• will not save when the flow navigates from an HTTP/Email step to the next one.
• will not save when the flow is completed.

Screenflows consisting of an Email step followed by multiple sequential steps that are performed by an anonymous user bring the user back to the flow at the current/latest anonymous step if the Save on Navigate feature is selected.

Configuring Save on Navigation

This feature can also be turned on globally, If configured on a server level, it will apply to all workflows. You must modify configuration parameters to turn on this feature. If you want to save workflow steps that are partially filled in to the Task List, enable the Save/Load feature in your workflow. 

Show in History

If this checkbox is unchecked, tasks for the form or flow will not appear in Task History searches. If you want them to appear, make sure this box is checked. Checking or Un-checking it affects all tasks including ones that were created prior to the action.  

Task for First Step

This feature is useful for auto-starting flows programmatically. For example if you need to process a batch of invoices whose metadata is a row in a .csv file:

• you can programmatically process the csv file and auto-start a new flow for each row in the .csv.
• Initialize the form fields with data from the csv.

Another use case may be for a person in the HR department to auto-start a employee performance review by placing new review forms on each manager's task list for each of their reporting employees.

If this checkbox is unchecked and the flow requires a specific role or user to execute the 1st step then a person who tries to use the flow and does not have the required role or is not the specific user will get an error message:

...

If this checkbox is checked, and a person without the correct user or role tries to use the flow, the flow will be auto-started and sent to the task list of the person(s) specified in the user property or the roles list. The user who tried to access the flow will see the Pending Message setup for the first step or the default pending message "Your Request is being processed".

This feature is useful for auto-starting flows programmatically. For example if you need to process a batch of invoice whose metadata is a row in a .csv file. You can programmatically process the .csv file and auto-start a new flow for each row in the .csv initializing the form fields with data from the .csv.

...

Kick Off Parallel Workflow Tasks

It is possible to "kick off" a workflow from a form by using a business rule that performs an http get with the URL to the workflow. The Task for First Step property must be checked in the workflow for this to work. If you are using v7.2+, the raw link to the workflow that you are calling must be in the format discussed below:

• Cloud customers must change http://app.frevvo.com to frevvo:// in the rule that kicks off the flow.
• In-house customers must change the http:<domain>:<port> to  frevvo:// in the rule that kicks off the flow.

Fast Finish

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 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. 

...

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 the  Accessibility 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.

...