Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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, frevvo 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 [[V4_Designing_Forms#Tracking_Id | Tracking Id]] described  described in designing forms.====

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 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 [[V4_Designing_Forms#Setup_Key.2FSaved_Fields | Setup Key/Saved Fields]] documentation  documentation for forms for details on these fields.'''

Summary Fields

...

<br style="clear:both;"/>
You may select the fields you want to appear in the Summary view if you have a Summary step in your flow. Only checked fields will appear in the Summary.==== <span id="flowPrintable">Printable</span> ====

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

Flows do not current 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 [[V4_Using_Forms#Printing_Forms | Printing Forms]].

Each activity also has a printable property which controls whether or not that activity appears in the [[V4_Integration#PDF_Integration | PDF document view]]. See [[#Printable_2 | activity printable]] for  for full details.====

Save PDF

...

When checked a PDF image of the flow is saved in frevvo's submission repository. See the documentation for the [[V3_Viewing_Form_Submissions#Viewing_PDFs | 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 activities or a combination of the two, it is important to understand what controls will be printed with the PDF is generated. See the topic discussing the [[#Printable_2 | the activity printable property]].====

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.

Save/Load

If you check this checkbox a Save button will be displayed for each step in your flow. If you don’t want users to be able to save partially completed flows and continue them later, uncheck the checkbox so users will not see this button.

...

If you are not authenticated, clicking the Save button will display an authentication dialog that requires you to login. See [[V4_Using_Forms#Save.2FLoad | the documentation on using forms and flows]] for  for more details.

Users can repeat the save/load steps as many times as they wish.

Saved flows are not the same as submitted flows. Saved flows do not appear in the Submissions Repository. Saved flows can contain invalid data and can also contain required fields with no values yet entered. When such a flow is re-loaded the missing and invalid values are again flagged as such by frevvo. And the flow cannot be continued/finished until corrections are made to those fields.====

Show in History

...

If this checkbox is unchecked, tasks for the form or flow will not appear in [[V4_Tasks_Home_Page#Search_History | 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

...

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

Code Block
Error

...


Access Denied. Either you are not authenticated or you do not have the proper permissions/role.

...

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

...

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

Force Auth

...

See [[V4_Designing_Forms#Force_Auth | Force Auth]] described  described in designing forms.