...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
By default all workflow descriptions say, “Edit the workflow to change this description,” but you can change this if you wish. You also see this description when you view individual submission documents. The Description is limited to 255 characters.
Navigation
can automatically generate and display a navigation toolbar for your workflow which users can use to navigate back and forth between workflow steps. There are four available options:
...
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 workflow... 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 workflow. 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 workflow will open up at step B.
Here is a short synopsis of when the current location is saved. Consider a workflow with the following steps/roles: Role1(A → B → C) → Role2(D) → Role3(E):
- The workflow 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 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 workflow 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 workflow is already saved in the db in the PENDING state.Role2 clicks continue: saves before the step is renderedPENDING state 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 workflow navigates from an HTTP/Anonymous Task step to the next one.
- will not save when the 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 workflow at the current/latest anonymous step if the Save on Navigate feature is selected.
Configuring Save on Navigation
...
If the PDF Name property is empty, then the form workflow name is used as the pdf 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.
...
- Edit the workflow in the Workflow designer.
- Click on the Employee Information step. Click on the
Edit Step Properties icon. Click the General Settings tab.
- Check Fast Finish.
- Repeat for all the steps in the workflow where you want the Finish button to display.
- Save your changes.
If the steps in your workflow consist of forms and/or a summary step, Fast Finish forwards through the steps of your workflow until it hits one of the terminating conditions listed above.
Let's consider the Employee On Boarding workflow as an example. This workflow consists of a screenflow that is filled in by the new employee:
...
The Fast Finish button on an iPhone or iPad is accessed via a dynamic action menu that is activated by the right-most button in the top button bar. The action menu drops down below the button and floats above the form. If Fast Finish is not selected for the workflow or on the current step, then the action button and menu are not present at all.
Refer to this feature announcement for more information.
...
If this checkbox is unchecked, tasks for the form or workflow 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/workflows 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 workflow. Uncheck the checkbox to remove the logo from your workflow.
...