Section

Column

Properties Navigator

Clicking the Edit icon on the Flows Home page opens the workflow in the Flow Designer. The Properties Navigator panel displays in the lower-left portion of the Form Designer. This panel shows information about important properties setup for this flow step. Not all of the configured properties are shown in this view.

Open the Flow Properties wizard by:

Clicking inside a section or clicking on the Edit Flow Properties icon in a section of the Properties Navigator. This immediately displays the property tab for editing.
Clicking the Edit Flow Properties icon in the Flow Designer toolbar

The Properties Tabs work the same way whether you open them from the Navigator or from the Flow Designer toolbar. Here is what you need to know:

If you are working on several tabs at one time, you can navigate to other tabs and make changes there. Use the left and right arrows at the top of the screen to display additional tabs. You must click the Submit button when you are finished configuring Step Properties to save your changes. Remember to save the workflow.
will validate the Property Settings when you click Submit. If a property value is invalid, the tab(s) will not close and a message will display telling the designer that there are corrections to be made before saving. The screen will stay on the current tab if there is a validation error. Otherwise, another invalid tab will be auto selected (starting from left to right) if another tab needs attention. Tab labels with invalid entries display in red.
Clicking on the Cancel button closes the tab(s). You will be asked to confirm if any changes were made.
Hover over any field on the Properties tabs to see a helpful hint providing information about the property. Some fields contain instructions to guide you.
Clicking on the down arrow for a property shows an unfiltered list of choices applicable to that property. For some properties, you may see templatized controls from your flow and flow/special templates provided in .
In some cases, you can type ahead to narrow down the list. Use the up/down arrows, the Enter key or click an option with your mouse to select an option. Use the Backspace, Delete or click the x on a selected property to delete it.
Typing a opening curly brace into some fields, followed by the name of a control, show a list of the fields in your flow that match the entered text and will be added to the field as a control template.
On some tabs, you may have to slide the toggle to the right to turn on a feature.

Each flow property setting is described below.

Column

width	400px

On This Page:

Table of Contents

maxLevel	1

...

Configuring the Save on Navigate feature enables the screenflow to be completed in multiple sessions.

Excerpt

Let's consider a Job Application workflow with the following requirements:

The workflow is going to be performed by anonymous users. Anonymous users do not sign in to .
The anonymous user receives an email that includes a link to the workflow.
The workflow must collect a lot of information from the applicant: Contact Information, Education and Employment history, References and more. You can create one long form or design a screenflow with an Anonymous Task step and subsequent steps as separate screens to collect the information.
The user must have the option to compete the screenflow in multiple sessions. Clicking on the email link takes the user back to the last step in the screenflow where the Continue button was clicked.
The user must be able to navigate back to previous steps to review or update information that was previously entered.

Flow Designer

The Save on Navigate checkbox is checked and the Navigation Toolbar is configured on the Flow Property Panel
Step 1 of the screenflow has a field named EmailAddress that collects the applicant's email address.
Step 2 is assigned to an email address. This is the first step that is performed by the anonymous user.
All remaining steps in the screenflow are designed to collect the applicant's information: Contact Info, Education and Employment history, references etc. Remember, the anonymous user does not login to perform these steps so they cannot have a role, dynamic role or user property assigned to them.

The image shows an example of a possible screenflow design:

Image Modified

Use Mode

Anonymous users return to a previous step by clicking on the Navigation Toolbar if the workflow contains a screenflow performed by an anonymous user.

Image Modified

Deployment

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

...

Designers should refer to the Save and Load topic for the details.

Save on Navigate

Imagine you are entering data into a large screenflow and something happens that causes you to navigate away from the flowworkflow... you just lost all your work! . Checking the Save on Navigate property , saves the task to your Task List. automatically "bookmarks" your place in the flowworkflow. Users You can go to their your Task List to retrieve the task and they will be returned to the screen where they you were when the browser was closed.

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 workflow will open up at step B.

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

The flow is instantiated and step A is renderedA user in Role1 starts the workflow on Step A: does not save because it is the FIRST step (if the user abandons the flow workflow in the browser it is as if it never existed).
The user clicks next: saves BEFORE step B renders.
The user performs Step B and C, then clicks next: does not save because the role change will do a save to the db in the PENDING stateworkflow will already be saved in the PENDING state due to the new role assignment on Step D.
Role2 performs the taskStep D and clicks continue: no need to save here since the flow workflow is already saved in the db in the PENDING state.Role2 clicks continue: saves before the step is renderedstate due to the new role assignment on Step E.
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 workflow navigates from an HTTP/Anonymous Task step to the next one.
will not save when the flow workflow is completed.

...

, because it will already be saved in the SUBMITTED state.

When Save on Navigate is used on a screenflow with sequential steps performed by an anonymous user bring , it brings the user back to the flow workflow at the current/latest anonymous step if the Save on Navigate feature is selected.

Configuring Save on Navigation

...

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.

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.

Show Logo

This property is checked by default and causes the “powered by frevvo” logo to appear on your flow. Uncheck the checkbox to remove the logo from your flow.

...

Access the Saved Fields tab by clicking the Edit Flow Properties icon on the Flow Designer toolbar. This will launch the Flow Properties wizard. Click the Saved Fields tab.
This tab does not appear in the Properties Navigator.
Select the Available Fields and use the arrow buttons to move them to the Saved Fields list. Drag and drop is available for some browsers.
Hover over a field in the list to see the step of the workflow where the control is located.
Click the Submit button to save the changes or navigate to another tab.

Excerpt

Saved Fields tab

This Saved Fields tab displays only when the Legacy Submissions view is configured as it is in the cloud. The only reason to configure Saved Fields for a form/flow is if you want to use the Export to Excel which is only available in the Legacy Submissions view. Remember, Saved Fields are stored in the database when the form/flow is completed. This can significantly reduce performance, especially for large forms and require additional storage in the repository.

Warning

The Export of submissions to Excel feature has been replaced by the Download to CSV. If you have not used the Export to Excel feature in the past, we recommend that you become familiar with the Download to CSV .

You can still use the Export to Excel feature by accessing it from the Submissions Legacy view. However, the Legacy Submissions view and the Export to Excel may be removed in a future release.

In-house customers can choose to hide the Legacy Submissions view with a configuration parameter. If the Legacy submission view is not visible, the Saved Fields tab is not displayed in the Form/Flow designers and the Export to Excel feature is not available.

Refer to Submissions Stored Inside of Live Forms - Legacy View for the details about the Legacy Submission view and the Export to Excel feature.

Versions Compared

Old Version 30

New Version 31

Key