| Section |
|---|
| Column |
|---|
Each flow property setting is described below.
|
| Column |
|---|
Each flow property setting is described below.
|
| Column | ||||
|---|---|---|---|---|
| ||||
On This Page:
|
...
| Excerpt | |||||
|---|---|---|---|---|---|
Anonymous Screen Flow Navigation
A screenflow is a type of workflow consisting of a collection of sequential steps performed by the same user. What if you wanted that user to be anonymous? Configuring the Navigation Toolbar in an anonymous screenflow allows anonymous users to navigate back to a previous step in a screenflow. The set of available links is restricted to the steps that are executed in sequence by the anonymous user. Links to steps outside of the screenflow are not visible. The steps in the screenflow cannot have a role, dynamic role or user property assigned to them. Configuring the Save on Navigate feature enables the screenflow to be completed in multiple sessions. Let's consider a Job Application workflow with the following requirements:
Flow Designer
The image shows an example of a possible screenflow design: Use ModeAnonymous Users can return to a previous step by clicking on the Navigation Toolbar.
|
...
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):
...
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
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:
| 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".
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.
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 employeesThis 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:
| 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".
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.
...