| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Each option is discussed below. The form's Access Control dictates it's visibility regardless of share options; if you want it to be public, be sure to select Who can start the form? = Anyone (login not required).
Three options (Embedded Form/Workflow, Full Page/Pop Up and Just the iframe) are different ways to let users submit the form from your website without having to navigate elsewhere. These options have associated code on the left which can be cut and pasted into your website. Specific instructions for the code also are provided.
...
As users fill out forms and workflows, the values entered into form fields are cached on the server until the form is submitted or until the user's session times out. Each time you navigate a browser to a form link you will see a new form/workflow instance. The fields on the new instance will be empty or may contain default values, values from your back-end system, or values set by a business rule. If you close your browser window/tab and open the form via the share URL again, you will again get a new form/workflow instance.
...
Anonymous users can access public forms that include the save/load feature or digital signatures. These features require a login. When the anonymous user clicks to save or sign, they will be prompted with the login screen.
Approval Workflows
Approval workflows are very easy to automate in . The requester fills out the original form (or set of forms) electronically and the workflow is then routed it to the appropriate person or persons according to the desired business scenario. They’re notified with an email and can take action instantly using any device e.g. instant approval using a smartphone. E-signatures are collected and PDFs can be generated along the way. offers multiple integration options so you can save your data.
Approving a Task
Reviewing a task for approval is very easy in using the Task List. The approver can use the 
Quick Approval or the 
Perform icons to display the approval step. Quick Approval displays a Quick View of the task without displaying the entire form. It allows the user whose responsibility it is to review the task (manager, supervisor, reviewer, etc.) to add a comment, approve or reject, sign, and pass it to the next user in the workflow. This works well on mobile devices. If the approver wants to see the entire form they can click the Details button.
Follow these instructions to approve a task for the workflow that you downloaded:
...
A non-admin user can send a task back to a previous step by clicking the Reject button. The Reject button is configurable by the designer so all steps in the workflow may not have one.
Let's consider an Expense Report workflow where the first step is performed by the employee, then it is routed to the employee's manager for approval/rejection. If approved, the workflow is then routed to the Payroll department for final processing. A Reject button has been configured for the Manager and Payroll steps and email notification is turned on for all participating users. Visit the Reject to Revise documentation to see an example rejection scenario.
...
The designer defines task boundaries by setting assignments (user, role or email address), so each workflow step with an assignment is considered a new task. Any subsequent workflow steps without assignment are considered part of screen workflow of the same task. Having an assignment to a workflow step strictly enforces the task boundary and it is applicable for the first step of workflow as well.
...
| Note |
|---|
When navigating back using the navigation bar, consecutive unassigned tasks in a screenflow will be available to edit. Once a user has moved on to a subsequent assigned step, all prior steps will be read-only. |
Invalid Task Assignment
...
- Configure Task Notification emails - users receive an email informing them that there is a task on their Task List that requires their attention.
- Send an email when a workflow is completed. This email is configured through the Doc Action wizard and can be customized.
- Send an email when one of the steps in the middle of the workflow is executed. This email is configured through the Activity Doc action wizard and can be customized.
- An email is sent to a user when a task is rejected. This is an automatic function of the rejection feature and the email cannot be customized at this time.
- Escalation emails for tasks that must be completed before a deadline. Designers configure the users that receive reminder emails and an email that is sent when the deadline expires.
- Route a workflow to someone who does not have a frevvo login (anonymous user.) Refer to the Workflow Tutorial for step by step instructions to implement this feature for a Purchase Order workflow.