| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The visibility field has been removed from the flow property pane in the Live Forms Flow designer. Flow Visibility is selected via the Access Control List wizard. You can access the wizard by clicking on the 
icon icon for your flow on the Flows Home Page . If you are in the flow designers, click the
icon icon in the toolbar to display the wizard. Flow Visibility has the same meaning as Visibility for forms. The one exception is the custom option which is not provided for flows. The default value for flows is Public in Tenant.
...
This is the message that is displayed on the screen during a workflow when the next step must be performed by a different user/role and puts it on that user's task list. For example, in an Vacation Request workflow, the first step may be filled in by an Employee but the second step (approval) must be signed by a Manager. When the Employee clicks Continue, will put the task on the Manager's task list and display this message on the Employee's screen. This message can use templatized strings for dynamic content, e.g. the message can be set to "Thank You {FirstName} {LastName}. Your request has been submitted to your manager for approval." 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 pending message using the actual values of the FirstName and LastName fields e.g. "Thank You Tom Smith. Your request has been submitted to your manager for approval.".
Tracking Id
See Tracking Id described in designing forms.
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.
Printable
If you check a flow's printable checkbox a Print button will be displayed in Summary steps of the flow. If you don’t want users to print your flow, uncheck the checkbox so users will not see the Print button. You can control which fields are printed by setting up which fields are displayed in the Summary View as described below.
Flows do not currently support a print icon as is available on forms. This will be added in an up coming release. One solution is to add your own print link as discussed in the chapter Printing Forms.
Each step also has a printable property which controls whether or not that step appears in the PDF document view . See the printable property for workflow steps for full details.
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 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 repositoryThis property can be set at the flow or flow step level. If you set up a message at the flow level, it will display after the Continue button is clicked on each step of the flow except for the last one. On the last step, you will see the default message, "Thank You!. Your submission has been received" unless you customized the message using the Form Action wizard.
To set up a message at the flow level, follow these steps:
- Click the
icon for your flow on the Flow Home page.
- Click the Toolbar to display the flow properties pane.
- Type your message in the Pending Msg box.
This will work if you want the same message to display for all of the steps of your flow. Typically, designers want to display different customized messages after each step. If this is the case, you must set the Pending Message at the flow step level.
Tracking Id
See Tracking Id described in designing forms.
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.
Printable
If you check a flow's printable checkbox a Print button will be displayed in Summary steps of the flow. If you don’t want users to print your flow, uncheck the checkbox so users will not see the Print button. You can control which fields are printed by setting up which fields are displayed in the Summary View as described below.
Flows do not currently support a print icon as is available on forms. This will be added in an up coming release. One solution is to add your own print link as discussed in the chapter Printing Forms.
Each step also has a printable property which controls whether or not that step appears in the PDF document view . See the printable property for workflow steps for full details.
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 the submissions user interface, you can 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.
...
- Signature
- Formviewer
- PageBreak
- Message
- Link
- Trigger
- Image
- Video
Save PDF
When checked a PDF image of the flow is saved in ' submission repository. See the documentation for the submissions repository for details on viewing the PDFs saved there.
Since flows are a combination of multiple forms or a single form visible in multiple steps or a combination of the two, it is important to understand what controls will be printed when the PDF is generated. See the topic discussing the step printable property. Notice all controls, including those disabled or in a signed section, are no longer grayed out in the pdf.
PDF Name
When you check Save PDF on the flow Property panel, an optional PDF name field displays. It is only visible when the "Save PDF" property is checked and is disabled when the "Save" property is unchecked. If this new property is set, then it is used to name the generated PDF. You can use templates to name the pdfs.For example, let's say you have an Employee Onboarding flow for new employees and you wanted the pdf in the submissions to be named using their last name. Simply add the name of the control in your flow that collects the last name as a template ex:{LastName} in the PDF Name property. The pdf for each Employee Onboarding submission will then be named {LastName}.pdf.
If the PDF Name property is empty, then the form name is used as the pdf name. It is recommended that PDF Names use characters that are suitable for filenames. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works.
In the submission, the pdf for the Onboarding for new hire Eric Armani is named as shown as shown:
checked a PDF image of the flow is saved in ' submission repository. See the documentation for the submissions repository for details on viewing the PDFs saved there.
Since flows are a combination of multiple forms or a single form visible in multiple steps or a combination of the two, it is important to understand what controls will be printed when the PDF is generated. See the topic discussing the step printable property. Notice all controls, including those disabled or in a signed section, are no longer grayed out in the pdf.
PDF Name
When you check Save PDF on the flow Property panel, an optional PDF name field displays. It is only visible when the "Save PDF" property is checked and is disabled when the "Save" property is unchecked. If this new property is set, then it is used to name the generated PDF. You can use templates to name the pdfs.For example, let's say you have an Employee Onboarding flow for new employees and you wanted the pdf in the submissions to be named using their last name. Simply add the name of the control in your flow that collects the last name as a template ex:{LastName} in the PDF Name property. The pdf for each Employee Onboarding submission will then be named {LastName}.pdf.
If the PDF Name property is empty, then the form name is used as the pdf name. It is recommended that PDF Names use characters that are suitable for filenames. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works.
In the submission, the pdf for the Onboarding for new hire Eric Armani is named as shown as shown:
| Tip |
|---|
Avoid special characters when specifying the PDF Name. If you are using a template where users enter characters for the PDF Name, you will need to write a rule to handle the special characters by escaping them.For example, entering Cable & Wireless into a field in your form that is being used as a template for the PDF name requires a rule to escape the & (and any other special characters) from the control. |
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.
...
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):
...
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. You can find a discussion of this topic here.
Configuring Save on Navigation
...
If Fast Finish, is selected on the flow or step level, the user can click the Finish button after making the correction and the flow will fast forward through Step 6. Fast Finish will stop here since step 7 is assigned to the user Sue who is a member of the Human Resources department. The user will see the pending message after Step 6 and the workflow will be routed to Sue for final processing.
If the Fast Finish and Save/Load features are enabled for a workflow, the user can save a partially completed form to their task list. If the saved form still has required fields that have to be filled in, when the user retrieves the saved task from their task list to complete and submit it, clicking the Fast Finish button takes the user to the point in the screen flow where they left off.
...
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.
...