| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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 repository.
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.
...
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.
| Info |
|---|
In a flow, controls are listed in the Available and Saved Lists using the control name. If you change the name of a control in a flow step, it will unset the saved field. The newly renamed control will now show on the Available list and the designer must move it to the Saved List again by clicking on the Setup/Key/Saved/Summary Fields wizard. |
...
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:
...
.
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):
...
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.
...